Post-quantum cryptography side chain

ABSTRACT

A computing entity accesses one or more blocks of a blockchain, encrypts the content of the one or more blocks using a first cryptographic technique to generate one or more first encrypted block values, and writes a first side chain block comprising the one or more first encrypted block values and a first signature to a first side chain. The computing entity accesses at least one of (a) at least one block of a particular second set of one or more second sets of the plurality of blocks or (b) one or more first side chain blocks corresponding to blocks of the second set, encrypts the content of the accessed block(s) using a second cryptographic technique to generate at least one second encrypted block value, and writes a second side chain block comprising the at least one second encrypted block value and a second signature to a second side chain.

TECHNOLOGICAL FIELD

Example embodiments of the present disclosure relate generally tocryptography and, more particularly, to systems and methods forproviding post-quantum cryptography (PQC). For example, exampleembodiments relate to the storage of PQC protected information/data by athird party.

BACKGROUND

Although still in its infancy, quantum computing and its boundlesspotential applications are of rapidly increasing interest to a broadarray of industrial sectors, including simulation, artificialintelligence, healthcare, and financial services. Unlike classicalcomputers, which process information in bits that can only represent oneof two binary information states at a time, quantum computers processinformation in quantum bits (qubits) that can represent a coherentsuperposition of both binary information states at the same time.Further, two or more qubits may be entangled so that their physicalproperties are correlated even when separated by large distances, andquantum computers may simultaneously perform a vast number of operationson these entangled qubits. This massive parallelism allows quantumcomputers to perform incredibly complex calculations at speedsunimaginable today and solve certain classes of problems that are beyondthe capability of today's most powerful supercomputers.

Reflecting this broad potential impact, companies from a variety ofmarket sectors are investing substantial resources to develop thesepromising quantum computing theories into real-world quantum computingcapabilities. However, this heightened interest and investment has yetto produce an enduring and functional quantum computer outside of alaboratory environment.

Nonetheless, there is widespread agreement among experts that quantumcomputers will disrupt current security protocols that protect globalfinancial markets and governmental institutions. For example, mostcommon public-key cryptography schemes, such as the widely-usedRivest-Shamir-Adleman (RSA) and Diffie-Hellman (DH) schemes, rely on theinability of classical computers to complete certain types of complexmathematical calculations, such as integer factorization and discretelogarithm computation, respectively, within a reasonable amount of time.However, a quantum computer implementing Shor's algorithm potentiallycould complete these complex calculations in a relatively short time andthereby determine the private keys used for current public-key systemsfrom the corresponding public keys. Accordingly, there is an urgent needfor data owners and hosting services to begin migrating their data andupgrading their systems to use quantum-resistant algorithms beforequantum computing capabilities are realized. Moreover, as Cloud-basedcomputing and Cloud-based data storage becomes more prevalent, it willbe important for data owners to be able to secure their data even whenthat data is stored by a third party (e.g., in Cloud-based storage).

BRIEF SUMMARY

Computing systems, computing apparatuses, computer-implemented methods,and computer program products are disclosed herein for improved securityof data stored by third parties. For example, various embodimentsprovide computing systems, computing apparatuses/entities,computer-implemented methods, and/or computer program productscorresponding to the secure storage of data in third party operatedcomputer readable memory. In various embodiments, post-quantumcryptography (PQC) encryption techniques are used to aid in securing thethird party-stored data.

According to a first aspect of the present disclosure, a method foroperating a ledger system is provided. In an example embodiment, themethod comprises accessing, by a computing entity, one or more blocks ofa blockchain comprising a plurality of blocks, the plurality of blockscomprising one or more non-overlapping first sets of blocks. Each firstset of blocks comprises a first number of consecutive blocks. The one ormore blocks are from a particular one of the one or more first sets. Themethod further comprises encrypting, by the computing entity, thecontent of the one or more blocks using a first cryptographic techniqueto generate one or more first encrypted block values; and writing, bythe computing entity, a first side chain block comprising the one ormore first encrypted block values and a first signature to a first sidechain. The method further comprises accessing, by the computing entity,at least one of (a) at least one block of a particular second set of oneor more second sets of the plurality of blocks or (b) one or more firstside chain blocks corresponding to blocks of the particular second set.The second sets of blocks are mutually non-overlapping and each secondset of blocks comprises a second number of consecutive blocks of theplurality of blocks. The method further comprises encrypting, by thecomputing entity, the content of at least one of (a) the at least oneblock or (b) the one or more first side chain blocks using a secondcryptographic technique to generate at least one second encrypted blockvalue; and writing, by the computing entity, a second side chain blockcomprising the at least one second encrypted block value and a secondsignature to a second side chain.

According to another aspect of the present disclosure, an apparatus isprovided. In an example embodiment, the apparatus comprises processorcircuitry. The processor circuitry is configured to access one or moreblocks of a blockchain comprising a plurality of blocks. The pluralityof blocks comprise one or more non-overlapping first sets of blocks.Each first set of blocks comprises a first number of consecutive blocks.The one or more blocks are from a particular one of the one or morefirst sets of blocks. The processor circuitry is further configured toencrypt the content of the one or more blocks using a firstcryptographic technique to generate one or more first encrypted blockvalues; and write a first side chain block comprising the one or morefirst encrypted block values and a first signature to a first sidechain. The processor circuitry is further configured to access at leastone of (a) at least one block of a particular second set of one or moresecond sets of the plurality of blocks or (b) one or more first sidechain blocks corresponding to blocks of the particular second set. Thesecond sets of blocks are mutually non-overlapping and each second setof blocks comprises a second number of consecutive blocks of theplurality of blocks. The processor circuitry is further configured toencrypt the content of at least one of (a) the at least one block or (b)the one or more first side chain blocks using a second cryptographictechnique to generate at least one second encrypted block value; andwrite a second side chain block comprising the at least one secondencrypted block value and a second signature to a second side chain.

According to yet another aspect of the present disclosure, a computerprogram product is provided. In an example embodiment, the computerprogram product comprises at least one non-transitory storage mediastoring executable instructions. The executable instructions compriseexecutable code portions configured to, when executed by the processingcircuitry of an apparatus, cause the apparatus to access one or moreblocks of a blockchain comprising a plurality of blocks. The pluralityof blocks comprise one or more non-overlapping first sets of blocks.Each first set of blocks comprises a first number of consecutive blocks.The one or more blocks are from a particular one of the one or morefirst sets of blocks. The executable instructions comprise executablecode portions are further configured to, when executed by the processingcircuitry of an apparatus, cause the apparatus to encrypt the content ofthe one or more blocks using a first cryptographic technique to generateone or more first encrypted block values; and write a first side chainblock comprising the one or more first encrypted block values and afirst signature to a first side chain. The executable instructionscomprise executable code portions are further configured to, whenexecuted by the processing circuitry of an apparatus, cause theapparatus to access at least one of (a) at least one block of aparticular second set of one or more second sets of the plurality ofblocks or (b) one or more first side chain blocks corresponding toblocks of the particular second set. The second sets of blocks aremutually non-overlapping and each comprise a second number ofconsecutive blocks of the plurality of blocks. The executableinstructions comprise executable code portions are further configuredto, when executed by the processing circuitry of an apparatus, cause theapparatus to encrypt the content of at least one of (a) the at least oneblock or (b) the one or more first side chain blocks using a secondcryptographic technique to generate at least one second encrypted blockvalue; and write a second side chain block comprising the at least onesecond encrypted block value and a second signature to a second sidechain.

The foregoing brief summary is provided merely for purposes ofsummarizing some example embodiments illustrating some aspects of thepresent disclosure. Accordingly, it will be appreciated that theabove-described embodiments are merely examples and should not beconstrued to narrow the scope of the present disclosure in any way. Itwill be appreciated that the scope of the present disclosure encompassesmany potential embodiments in addition to those summarized herein, someof which will be described in further detail below.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying figures, which are not necessarily drawn to scale,illustrate embodiments and features of the present disclosure. Togetherwith the specification, including the brief summary above and thedetailed description below, the accompanying figures serve to explainthe embodiments and features of the present disclosure. The componentsillustrated in the figures represent components that may or may not bepresent in various embodiments or features of the disclosure describedherein. Accordingly, some embodiments or features of the presentdisclosure may include fewer or more components than those shown in thefigures while not departing from the scope of the disclosure.

FIG. 1 illustrates a system diagram of a set of devices that may beinvolved in some example embodiments described herein;

FIGS. 2A, 2B, and 2C illustrate schematic block diagrams of examplecircuitries that may perform various operations, in accordance with someexample embodiments described herein;

FIGS. 3A, 3B, 3C, 3D, and 3E illustrate example PQC system architecturesconfigured to perform various operations, in accordance with someexample embodiments described herein;

FIG. 4 illustrates an example blockchain and side chain architecture, inaccordance with some example embodiments described herein;

FIG. 5 illustrate an example flowchart for generating a blockchain andcorresponding side chains, in accordance with some example embodimentsdescribed herein;

FIG. 6A illustrates an example block of a primary chain of an exampleblockchain and side chain architecture, in accordance with some exampleembodiments described herein; and

FIG. 6B illustrates an example first side chain block of a first sidechain of an example blockchain and side chain architecture, inaccordance with some example embodiments described herein;

FIG. 6C illustrates an example second side chain block of a second sidechain of an example blockchain and side chain architecture, inaccordance with some example embodiments described herein.

DETAILED DESCRIPTION

Some embodiments of the present disclosure will now be described morefully hereinafter with reference to the accompanying figures, in whichsome, but not all embodiments of the disclosures are shown. Indeed,these disclosures may be embodied in many different forms and should notbe construed as limited to the embodiments set forth herein; rather,these embodiments are provided so that this disclosure will satisfyapplicable legal requirements. Like numbers refer to like elementsthroughout.

Overview

As noted above, methods, apparatuses, systems, and computer programproducts are described herein that provide for secure storage of data byan external data repository, such as a Cloud-based storage system and/orother third party operated data storage. Various embodiments provide forsecured storage of data by an external data repository that is secureagainst cryptanalytic algorithms implemented on a quantum computer.

Traditionally, data owners and third-party hosting services use hybridcryptosystems to safeguard the confidentiality, integrity, andauthenticity of enormous volumes of protected data and complex ITsystems. These hybrid cryptosystems typically use a combination ofasymmetric cryptography (e.g., public key cryptography), such as theRivest-Shamir-Adleman (RSA) cryptosystem, and symmetric cryptography(e.g., secret key cryptography), such as the Advanced EncryptionStandard (AES). One example of a modern hybrid cryptosystem is theTransport Layer Security (TLS) protocol, which relies on asymmetriccryptography for authentication and key management to establish sessionkeys, and symmetric cryptography for session encryption and integrityvalidation.

However, these cryptosystems are vulnerable to cryptanalysis algorithmsand/or attack algorithms implemented on quantum computers. For instance,asymmetric encryption, key exchange, and digital signature rely onmathematical problems such as the integer factorization problem (e.g.,as used in RSA) and the discrete logarithm problem (e.g., as used inDigital Signature Algorithm (DSA), Elliptic Curve DSA (ECDSA),Diffie-Hellman (DH), and Elliptic Curve DH (ECDH)). It is widelybelieved that a large-scale fault tolerant quantum computer couldeffectively break modern public key cryptosystems by solving instancesof the integer factorization problem and the discrete logarithm problemquickly enough that the keys determined based on those solutions arestill in use. For example, keys may be periodically changed such that ifit takes a long time to determine a key using a cryptanalysis algorithm,the key may no longer be in use by the time the key has been determined.However, if the key may be determined quickly via the cryptanalysisalgorithm, the key may still be in use and the determined key may beused to gain unauthorized access to information encrypted and/or digitalsignatures/certificates may be counterfeited via the determined key.

In one illustrative example, a quantum computer implementing Shor'salgorithm could determine the private keys used for current public-keysystems in a relatively short time because Shor's algorithm provides afaster cryptanalysis method for solving integer factorization than abrute force method (e.g., guessing prime numbers). For instance, Shor'salgorithm uses the quantum Fourier transform (QFT) instead of its slowerclassical counterpart, the fast Fourier transform (FFT). Further, Shor'salgorithm can be modified to compute discrete logarithms, includingdiscrete logarithms used for elliptic-curve cryptography (ECC).

In another illustrative example, a quantum computer implementingGrover's algorithm could effectively perform an exhaustive key searchbecause Grover's algorithm provides quadratic speedup and thereby couldbrute-force attack an N-bit symmetric cryptographic key in only about2^((N/2)) iterations. In some instances, for symmetric cryptographictechniques that support longer and/or multiple key lengths (e.g., AESsupports three key lengths a 128-bit key, 192-bit key, and 256-bit key),increasing the key length of the symmetric cryptographic key may providesufficient protection against Grover's algorithm because a brute-forceattack on a 2N-bit symmetric cryptographic key would require about 2^(N)iterations. For example, a 256-bit symmetric cryptographic key (e.g.,AES-256) may only provide 128 bits of security in a quantum computingenvironment. However, any migration plan that involves increasing thekey length of the symmetric cryptographic key must also evaluate theimpact of the longer key length on the performance of relatedapplications and the additional requirements of computational resources.

Although quantum computers capable of such feats are still believed tobe several years away, the threat of a “harvest now and decrypt laterattack” makes quantum computing an immediate real threat, even if thethreat will not be actionable until a sufficiently robust quantumcomputer is developed in the future. The “harvest now and decrypt laterattack” is a long-game attack where a bad actor scrapes, collects, orharvests (e.g., records and stores) encrypted data, such as datastreaming through the Internet or cloud, by the way of breaches orpassive interception and then hoard the encrypted data, waiting for theday when quantum computers can determine the cryptographic keys to theharvested data. This bad actor could be storing data to or from aspecific website, server, email client, or other target of attack or,given sufficient motivation and resources, recording petabytes of dataeach hour from general internet traffic. Once quantum computers arecapable of determining the cryptographic keys associated with theharvested encrypted data, the bad actor might use those cryptographickeys to decrypt the previously encrypted data. For instance, persistentdata, such as mortgage information and financial records, encrypted ordigitally signed with today's cryptographic algorithms will be at riskeven if the necessary quantum computing technology is not available forseven to ten years or even later. Subsequently, with advancements inartificial intelligence and machine learning and the exponentialincrease in data processing compute power, a bad actor could attack adata vault to extract meaningful information from the decryptedpetabytes of data.

These risks are amplified by the lengthy data retention requirements(e.g., security shelf-life) mandated by government agencies, such as theU.S. Federal Deposit Insurance Corporation (FDIC). For example, somedata records may need to be securely retained for decades or longer.

Given that data is a highly valuable asset, especially in the financialindustry, there is an urgent need for data owners and hosting servicesto initiate the process of protecting their valuable customerinformation and digital assets even before quantum computingcapabilities are realized. Moreover, as Cloud-based data storage andother external data repository use becomes more prevalent, data ownersmay wish to provide further protection for their data assets stored byexternal data repositories (e.g., data repositories that are operated byentities other than the data owner). This process primarily involvesmigrating data and systems to algorithms that are thought to bequantum-resistant. In an attempt to promulgate quantum-resistantalgorithms, the National Institute of Standards and Technology (NIST), afederal agency within the U.S. Department of Commerce, has initiated theNIST Post-Quantum Cryptography Standardization Process to solicit,evaluate, and standardize one or more quantum-resistant public-keycryptographic algorithms. At present, there are many different candidatecryptographic algorithms believed to be quantum-resistant. However,because the standardization process is not yet complete, migration ofclassical systems to any one of NIST's candidate cryptographicalgorithms could later compound the computational and resource burden ondata owners and hosting services if NIST does not select that particularcryptographic algorithm as the standard or makes changes to the proposedcryptographic algorithms.

Although some quantum-resistant cryptographic algorithms are availabletoday, those algorithms may not be the algorithm, or a variant of thealgorithm, that eventually is approved as part of the NIST Post-QuantumCryptography Standardization Process. Moreover, the adoption of thesealgorithms will, in some instances, be an overly complex andtime-consuming process. First, this migration process is challenging dueto the sheer volume of data consumed by these systems, as well as thegeneral complexity of the systems. For example, financial servicesproviders and their partners each may have data for millions ofcustomers and trillions of transactions stored in various databases. Inaddition, these providers are processing millions of transactions on adaily basis and adding new customer data to their systems. Second, datais stored in more places than ever before and must be encrypted usingdifferent cryptographic keys depending upon whether the data is going tobe protected while in transit, while at rest in-cloud, or while at reston-premises. Governmental regulations, NIST recommendations, andindustry standards and best practices will, in some instances, drive thecryptographic techniques that are used to encrypt the data. Third, manyorganizations use several types of encryption, hashing, and othercryptographic algorithms with varying security architecture depending onthe needs of the data owner or hosting service. Fourth, as various datarecords are required by government agencies to be securely retained forlong periods of time (e.g., decades or longer), there is the need toprotect data for varying durations to manage legal and regulatory risk,sometimes as long as twenty to thirty years, and even in some cases forover fifty years. Fifth, the deployment of fundamental changes toinfrastructure might take a decade or more, and there is very littletolerance for incurring risk while deploying changes. All of theseconsiderations introduce additional levels of complexity, and thus dataowners and hosting services must methodically migrate theircryptographic infrastructure to quantum-resistant cryptography. Inaddition, the cryptography transition is challenging because it is notrestricted only to algorithms and key lengths. Rather, the cryptographytransition is impacted by several other details of securityinfrastructure, such as interoperability, integration with existingsystems and security architectures, scalability, compliance andregulatory requirements, maintenance, and backward compatibilityrequirements.

In contrast to conventional cryptographic systems, the presentdisclosure relates to a post-quantum cryptography (PQC) system thatmitigates the vulnerability of traditional cryptographic algorithms byproviding techniques for migrating enormous volumes of data and complexIT systems to PQC technologies and platforms that are not vulnerable toattack by a quantum computer. The term “PQC” refers to cryptosystemswhich are, or are considered to be, resistant to attacks that use aquantum computer for cryptanalysis. In some embodiments, PQC techniquesinclude PQC communications channel-based cryptographic techniques,hash-based PQC techniques, lattice-based PQC techniques, isogeny-basedPQC techniques, code-based PQC techniques, multivariate-based PQCtechniques, zero-knowledge proof PQC techniques, other suitabletechniques, and combinations thereof (e.g., combinations of PQCcommunications channel-based cryptographic techniques with hash-based,lattice-based, isogeny-based, code-based, multivariate-based, orzero-knowledge proof PQC techniques).

Hash-based PQC techniques (e.g., hash-based PQC cryptographicsignatures) are suitable for one-time use, wherein a tuning parameterprovides a trade-off between signature size and key generation, signing,and verification speed, and can be can be used with any secure hashingfunction. Hash-based PQC techniques may be used to provide digitalsignatures, such as Leighton-Micali Signature (LMS), eXtended MerkleSignature Scheme (XMSS), and SPHINCS+.

Lattice-based PQC techniques are based on the shortest vector problem,the leading replacement for prime factorization and discrete logarithm,and typically are less computationally resource intensive in relation toisogeny-based and other PQC techniques. In some instances, lattice-basedPQC techniques may be used to provide digital signatures, such asDilithium and qTESLA. In some instances, lattice-based PQC techniquesmay be used to provide key exchange by key encapsulation, such asNewHope, Frodo Key-Encapsulation Mechanisms (FrodoKEM), Nthdegree-Truncated polynomial Ring Units (NTRU) Prime, and Kyber. In someinstances, lattice-based PQC techniques may be used to provide keyexchange by key agreement, such as NewHope Classic, Frodo Diffie-Hellman(FrodoDH), and Ring Learning With Errors Key EXchange (RLWE-KEX).

Isogeny-based PQC techniques use very small keys and typically are morecomputationally resource intensive in relation to lattice-based andother PQC techniques. In some instances, isogeny-based PQC techniquesmay be used to provide key exchange by key encapsulation, such asSupersingular Isogeny Key Encapsulation (SIKE). In some instances,isogeny-based PQC techniques may be used to provide key exchange by keyagreement, such as Supersingular isogeny Diffie-Hellman (SIDH) keyexchange.

Code-based PQC techniques use very large key sizes yet are typically thefastest PQC techniques at the comparable security level (e.g., extremelyfast in encryption and reasonably fast in decryption). In someinstances, code-based PQC techniques may be used to provide key exchangeby key encapsulation, such as Classic McEliece, McEliece Quasi-CyclicModerate Density Parity Check (QC-MDPC), and Bit Flipping KeyEncapsulation (BIKE).

Multivariate-based PQC techniques use small public keys and fastverification yet, in some instances, are less efficient than other PQCtechniques. Multivariate-based PQC techniques may be used to providedigital signatures, such as Rainbow.

Zero-knowledge proof PQC techniques use very small key pairs and derivetheir security entirely from the security of symmetric-key primitivesand are believed to be quantum-secure. In some instances, zero-knowledgeproof PQC techniques may be used to provide digital signatures, such asPicnic.

In some embodiments, the PQC system may retrieve one or more of thehash-based PQC techniques, lattice-based PQC techniques, isogeny-basedPQC techniques, code-based PQC techniques, multivariate-based PQCtechniques, and zero-knowledge proof PQC techniques from a remote serveror data storage device, such as the ISARA toolkit, the libOQS library,the libpqcrypto library, or a combination thereof.

PQC communications channel-based cryptographic techniques use PQCcommunications channels to secure transmission of sensitive orconfidential message data, such as Society for Worldwide InterbankFinancial Telecommunication (SWIFT) messages, International Organizationfor Standardization (ISO) 8583 messages, ISO 20022 messages, Internet ofThings (IoT) data, Health Insurance Portability and Accountability Act(HIPAA) data (e.g., electronic medical records, protected healthinformation), copyrighted content (e.g., electronic media, digitalrights management (DRM)-protected data files), and other suitablemessages. For example, the PQC system may be configured to implement aPQC communications protocol that transmits a first portion of anelectronic communication (e.g., message overhead data such as protocoloverhead, header data, metadata) to a client device over a firstclassical communications channel (e.g. non-PQC communications channel)and transmits a second portion of the electronic communication (e.g.,message payload data) to the client device over a second classicalcommunications channel (e.g., a PQC back channel such as a PQCout-of-band communications channel). In some embodiments, the firstclassical communications channel and the second classical communicationschannel may utilize different classical communications channels (e.g.,different communications networks, communications lines, communicationscircuitry, or a combination thereof). In some embodiments, the firstclassical communications channel and the second classical communicationschannel may utilize the same classical communications circuitry (e.g.,the same communications network, lines, hardware, infrastructure) but adifferent protocol, communications mechanism, network connector, orcombination thereof. For example, the PQC system may implement thenon-PQC communications channel as an in-band communications channel andthe PQC communications channel as an out-of-band communications channelusing the same communications infrastructure.

In one illustrative example, the electronic communication may be a SWIFTmessage, the first portion of an electronic communication may compriseSWIFT message overhead data, and the second portion of an electroniccommunication may comprise SWIFT message payload data. In anotherillustrative example, the first portion of the electronic communicationmay comprise a cryptographic data attribute indicative of a symmetriccryptographic technique, and the second portion of the electroniccommunication may comprise a symmetric cryptographic key, such as an AESsymmetric cryptographic key. The PQC system may be configured toauthenticate a session (e.g., perform a cryptographic handshake) withthe client device over the non-PQC communications channel based on thesymmetric cryptographic key that was transmitted to the client device,or a PQC add-on device coupled to the client device, over the PQCcommunications channel.

In yet another illustrative example, the first portion of the electroniccommunication may comprise a PQC indicator data structure thatidentifies the PQC communications channel and indicates that a secondportion of the electronic communication is to be transmitted over a PQCcommunications channel. The PQC indicator data structure may comprise alink or pointer to the PQC communications channel, a header thatidentifies the PQC communications channel as being out-of-band, otheridentification and routing information, or a combination thereof. Insome embodiments, the PQC indicator data structure may comprise a linkto the second portion of the electronic communication. In someembodiments, the first portion of the electronic communication maycomprise a TLS extension comprising the PQC indicator data structure. Inanother example, the first portion of the electronic communication maycomprise an ISO 8583 extension comprising the PQC indicator datastructure. In another example, the PQC indicator data structure may be,or comprise, or be indicated by, a PQC flag value. In another example,the PQC indicator data structure may comprise a link to a PQC electronicagreement (e.g., a bilateral agreement between the PQC system and theclient device to exchange confidential or sensitive data over a PQCcommunications channel) comprising the PQC indicator data structure.

In some embodiments, the PQC indicator data structure may comprise alink to a PQC shim configured to allow communication with the PQC system(e.g., via PQC callback circuitry comprised by the PQC system) over thePQC communications channel. For example, the PQC indicator datastructure may further comprise a PQC shim automatic installation controlsignal indicative of an electronic instruction for the client device toautomatically install the PQC shim based on the link. In anotherexample, the PQC indicator data structure may further comprise a PQCshim manual installation control signal indicative of an electronicinstruction for the client device to manually install the PQC shim basedon the link. In another example, the first portion of the electroniccommunication may comprise a PQC smart contract comprising the PQCindicator data structure.

In some embodiments, the first portion of the electronic communicationmay comprise a PQC request data structure (e.g., a request for anacknowledgment or confirmation that the client device is configured tocommunicate over a PQC communications channel). The PQC system may beconfigured to receive, in response to transmission of the PQC requestdata structure, a PQC acknowledgement data structure (e.g., anacknowledgment or confirmation that the client device is configured tocommunicate over a PQC communications channel) from the client deviceover the non-PQC communications channel. In response to receipt of thePQC acknowledgement data structure, to transmit the second portion ofthe electronic communication to the client device over the PQCcommunications channel.

In some embodiments, PQC indicator data structure may further identify aquantum communications channel and indicate that a quantum cryptographickey is to be transmitted over the quantum communications channel. ThePQC indicator data structure may comprise a link or pointer to thequantum communications channel, a header that identifies the quantumcommunications channel and comprises other identification and routinginformation. In some embodiments, the PQC indicator data structure maycomprise a link to the quantum cryptographic key. In some embodiments,the first portion of the electronic communication may comprise a TLSextension comprising the PQC indicator data structure. In anotherexample, the first portion of the electronic communication may comprisean ISO 8583 extension comprising the PQC indicator data structure. Inanother example, the PQC indicator data structure may be, or comprise,or be indicated by, a quantum flag value. In another example, the PQCindicator data structure may comprise a link to a quantum electronicagreement (e.g., a bilateral agreement between the PQC system and theclient device to exchange quantum information over the quantumcommunications channel) comprising the PQC indicator data structure.

In some embodiments, the first portion of the electronic communicationmay comprise a quantum request data structure (e.g., a request for anacknowledgment or confirmation that the client device is configured tocommunicate over a quantum communications channel). The PQC system maybe configured to receive, in response to transmission of the quantumrequest data structure, a quantum acknowledgement data structure (e.g.,an acknowledgment or confirmation that the client device is configuredto communicate over a quantum communications channel) from the clientdevice over the non-PQC communications channel. In response to receiptof the quantum acknowledgement data structure, the PQC system may beconfigured to transmit the quantum cryptographic key to the clientdevice over the quantum communications channel. Subsequently, the PQCsystem may be configured to authenticate a session (e.g., perform acryptographic handshake) with the client device over the non-PQCcommunications channel based on the quantum cryptographic key that wastransmitted to the client device over the quantum communicationschannel.

It is to be understood that each PQC technique may be implemented as avariant of a PQC cryptographic algorithm (e.g., based on NIST securitylevel). For example, the libOQS implementation of Dilithium includes thevariants Dilithium II (e.g., Dilithium_II_Medium), Dilithium III (e.g.,Dilithium_III_Recommended), and Dilithium IV (e.g.,Dilithium_IV_VeryHigh); and the ISARA Radiate Toolkit implementation ofDilithium includes the variants Dilithium 128 and Dilithium 160.Accordingly, the PQC technique for the PQC cryptographic algorithm“Dilithium” may be Dilithium II, Dilithium III, Dilithium IV, Dilithium128, or Dilithium 160. In yet another example, the ISARA Radiate Toolkitimplementation of FrodoKEM includes the variants FrodoKEM-976-AES andFrodoKEM-976-CSHAKE. In yet another example, the ISARA Radiate Toolkitspeed-optimized implementation of NewHope includes the variantLattice-based Unique Key Exchange (LUKE).

In some embodiments, the present disclosure relates to storage of databy an external data repository in a manner that is resistant and/orsecure against cryptanalytic algorithms implemented on a quantumcomputer. In various embodiments, the present disclosure relates to ablockchain and side chain system in which a first side chain storessigned and encrypted and/or verified data from blocks of the blockchainand a second side chain stores signed and encrypted and/or verified fromblock of the blockchain and/or first side chain blocks from the firstside chain. For example, the first side chain may use classical (e.g.,non-PQC) encryption techniques and/or signatures and the second sidechain may use PQC techniques and/or signatures. In various embodiments,PQC techniques are utilized so as to mitigate vulnerabilities fromquantum computers using Shor's algorithm, identification of techniquesto reduce the attack surface of cryptographic operations, and solutionsto other cascading opportunities and challenges identified herein thatstem from the vulnerability of today's common public-key encryptiontechniques to quantum computing.

Definitions

As used herein, the terms “data,” “content,” “information,” “electronicinformation,” “signal,” “command,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,and/or stored in accordance with embodiments of the present disclosure.Thus, use of any such terms should not be taken to limit the spirit orscope of embodiments of the present disclosure.

The term “comprising” means “including, but not limited to.” The termcomprising should be interpreted in the manner it is typically used inthe patent context. Use of broader terms such as comprises, includes,and having should be understood to provide support for narrower termssuch as consisting of, consisting essentially of, and comprisedsubstantially of.

The phrases “in one embodiment,” “according to one embodiment,” and thelike generally mean that the particular feature, structure, orcharacteristic following the phrase may be included in at least oneembodiment of the present disclosure and may be included in more thanone embodiment of the present disclosure (importantly, such phrases donot necessarily refer to the same embodiment).

The word “example” is used herein to mean “serving as an example,instance, or illustration.” Any implementation described herein as“example” is not necessarily to be construed as preferred oradvantageous over other implementations.

If the specification states a component or feature “may,” “can,”“could,” “should,” “would,” “preferably,” “possibly,” “typically,”“optionally,” “for example,” “often,” or “might” (or other suchlanguage) be included or have a characteristic, that particularcomponent or feature is not required to be included or to have thecharacteristic. Such component or feature may be optionally included insome embodiments, or it may be excluded.

The terms “processor” and “processing circuitry” are used herein torefer to any programmable microprocessor, microcomputer or multipleprocessor chip or chips that can be configured by software instructions(applications) to perform a variety of functions, including thefunctions of the various embodiments described above. In some devices,multiple processors may be provided, such as one processor dedicated towireless communication functions and one processor dedicated to runningother applications. Software applications may be stored in the internalmemory before they are accessed and loaded into the processors. Theprocessors may include internal memory sufficient to store theapplication software instructions. In many devices the internal memorymay be a volatile or nonvolatile memory, such as flash memory, or amixture of both. The memory may also be located internal to anothercomputing resource (e.g., enabling computer readable instructions to bedownloaded over the Internet or another wired or wireless connection).

For the purposes of this description, a general reference to “memory”refers to memory accessible by the processors including internal memoryor removable memory plugged into the device, remote memory (e.g., cloudstorage), and/or memory within the processors themselves. For instance,memory may be any non-transitory computer readable medium havingcomputer readable instructions (e.g., computer program instructions)stored thereof that are executable by a processor.

The term “computing device” is used herein to refer to any one or all ofprogrammable logic controllers (PLCs), programmable automationcontrollers (PACs), industrial computers, desktop computers, personaldata assistants (PDAs), laptop computers, tablet computers, smart books,palm-top computers, personal computers, smartphone, headset, smartwatch,and similar electronic devices equipped with at least a processorconfigured to perform the various operations described herein. Devicessuch as smartphones, laptop computers, tablet computers, headsets, andsmartwatches are generally collectively referred to as mobile devices.

The term “server” or “server device” is used to refer to any computingdevice capable of functioning as a server, such as a master exchangeserver, web server, mail server, document server, or any other type ofserver. A server may be a dedicated computing device or a computingdevice including a server module (e.g., an application which may causethe computing device to operate as a server). A server module (e.g.,server application) may be a full function server module, or a light orsecondary server module (e.g., light or secondary server application)that is configured to provide synchronization services among the dynamicdatabases on computing devices. A light server or secondary server maybe a slimmed-down version of server type functionality that can beimplemented on a computing device, such as a smart phone, therebyenabling it to function as an Internet server (e.g., an enterprisee-mail server) only to the extent necessary to provide the functionalitydescribed herein.

The term “post-quantum cryptography (PQC)” refers to cryptosystems whichare, or are considered to be, resistant to cryptanalytic algorithmsimplemented on a quantum computer. In some instances, the term PQCrefers to cryptography that may or will be secure even after thedevelopment of large-scale error tolerant quantum computing devices. Therelated term “PQC migration” refers to the migration of classicalcryptosystems to PQC cryptosystems and includes, but is not limited to,the updating of system software stacks and security infrastructure. Insome embodiments, PQC migration includes migration of classical systemsto PQC systems or hybrid systems (e.g., a combination of classical andPQC). In some embodiments, PQC migration includes translations ofnetworks. For example, today networks A, B, and C may only be able toutilize classic cryptography, but tomorrow network C may be able toutilize PQC so the PQC system may drop in a PQC gateway to translateback and forth such that eventually network B is PQC enabled, butnetwork A may never become PQC enabled so the PQC system may determinethat transactions to or from network A are a higher risk and implementthe PQC techniques described herein according to that higher risk.

The term “quantum basis” refers to sets of orthogonal quantum states,including, but not limited to, pairs of photonic polarization states.The pairs of photonic polarization states may comprise, for example, therectilinear, diagonal, and circular photonic polarization states. The“rectilinear basis” refers to the pair of rectilinear photonicpolarization states comprising the horizontal photon polarization state|0> and the vertical photon polarization state |1>. The “diagonal basis”refers to the pair of diagonal photonic polarization states comprisingthe diagonal photon polarization state of 45 degrees and the diagonalphoton polarization state |35 degrees. The “circular basis” refers tothe pair of circular photonic polarization states comprising the leftcircular photon polarization state |L> and the right circular photonpolarization state |R>.

The term “quantum particle” refers to photons, atoms, electrons,molecules, ions, or other suitable particles or quasi-particles (e.g.,composite fermions). The term “entangled quantum particle” refers to twoor more photons, atoms, electrons, molecules, ions, or other suitableparticles or quasi-particles entangled according to the principles ofquantum entanglement.

The term “qubit” refers to a basic unit of quantum informationcomprising a two-state, or two-level, quantum mechanical system, suchas: the polarization of a single photon (e.g., a photon encoded using aquantum basis as previously defined); the spin of a single electron(e.g., a spin qubit comprising the spin up state |1> and the spin downstate |0>); the energy level of a single atom (e.g., a superconductingqubit); the Hall conductance of electron systems (e.g., qubits based ona quantum Hall effect, such as an integer quantum Hall effect, afractional quantum Hall effect, or a quantum spin Hall effect); thevibration state of a single carbon nanotube or nanoparticle (e.g., acarbon qubit, a carbon nanotube or nanoparticle coupled to a spin qubit,a carbon nanotube or nanoparticle coupled to a superconducting qubit);the electronic state of an ion (e.g., a trapped ion); a transmissionline shunted plasma oscillation qubit (e.g., a fixed-frequency transmonqubit, a frequency-tunable transmon qubit); a charge qubit (e.g., asuperconducting charge qubit); a defect (e.g., a vacancy, a dopant, or acombination thereof, such as a nitrogen-vacancy center or asilicon-vacancy center) in a diamond structure (e.g., a diamond qubit);or any other suitable qubit. Qubits may exist in multiple statessimultaneously and can be made of any suitable quantum particle,including entangled quantum particles. Qubits may exist in multiplestates simultaneously and may be made of quantum particles such asphotons, atoms, electrons, molecules, ions, or other suitable particles,such as quasi-particles. In some embodiments, qubits may be entangledaccording to the principles of quantum entanglement. For example, a pairof entangled qubits may comprise a first entangled qubit and a secondentangled qubit, where measurement of the first entangled qubit causesthe collapse of the second entangled qubit such that the first entangledqubit and the second entangled qubit are equal (e.g., both “0” or both“1”) when measured using the same quantum basis.

The term “optical line” refers to an optical communications path. Forexample, an optical line may comprise an optical fiber, an opticalwaveguide, a fiberoptic cable, a non-polarization maintaining opticalfiber, an optical transmission line, a quantum line, or a combinationthereof. The term optical line broadly encompasses on-chip opticallines.

The term “quantum line” refers to a quantum communications path. Forexample, a quantum line may comprise a polarization-maintaining (PM)optical fiber (PMF or PM fiber), photonic transmission lines, photoniccrystals, photonic circuitry, free space (e.g., air, vacuum), or acombination thereof. In some embodiments, a PM fiber uses birefringenceto maintain the polarization states of photons. This is normally done bycausing consistent asymmetries in the PM fiber. Example PM fiber typesinclude: panda fiber which is used in telecom; elliptical clad fiber;and bowtie fiber. Any of these three designs uses birefringence byadding asymmetries to the fiber through shapes and stresses introducedin the fiber. This causes two polarization states to have differentphase velocities in the fiber. As such, an exchange of the overallenergy of the two modes (polarization states) becomes practicallyimpossible. The term optical line broadly encompasses on-chip quantumlines.

The term “on-chip encoder” and “on-chip decoder” is used herein to referto any device that respectively encodes or decodes a qubit ofinformation, or in time-bins of information, on a photon or an electron.In this regard, the qubit decoder may comprise an optoelectronic deviceas described below.

The terms “optoelectronic device,” “optoelectronic component,” “laserdevice,” “light source,” “single photon source,” “particle source,” andsimilar terms are used herein interchangeably to refer to any one ormore of (including, but not limited to, combinations of): a polarizedlight modulator (PLM); a polarized light demodulator (PLD); aquantization circuit; a laser device, such as a diode laser, a verticalcavity surface emitting laser (VCSEL), a semiconductor laser, afiberoptic laser, or an edge-emitting laser (e.g., a gallium arsenide(GaAs) edge-emitting laser comprising an indium gallium arsenide(InGaAs) quantum well); a light source; a single photon source; amodulator or modulating circuit; a photodetector device, such as aphotodetector, an array of photodetectors, or a photodetector panel; alight emitting device, such as a light emitting diode (LED), an array ofLEDs, an LED panel, or an LED display; a sensing device, such as one ormore sensors; any other device equipped with at least one of thematerials, structures, or layers described herein; an optical component,such as an optical lens, attenuator, deflector, phase shifter, filter,mirror, window, diffuser, prism, lenses, crystals (e.g., non-linearcrystals), wave plates, beam splitter, bit manipulator, polarizer, ordiffraction grating; an interferometer implemented as a Mach-Zehnderinterferometer (MZI), Fabry-Perot interferometer, Michelsoninterferometer, any other suitable configuration, or any combination orpermutation thereof; any device configured to function as any of theforegoing devices; or any combination thereof. In some embodiments, thelaser device may use a VCSEL to generate photons, qubits (e.g., bymodulating photons), or both. In some embodiments, a polarization pulseshaper may be integrated with the laser chip on the same laser device.In some embodiments, modulating circuitry (e.g., a modulating circuit)may be implemented on a board. Examples of a laser device may comprise afiberoptic laser with a polarizing component, an edge-emitting laser, aVCSEL, a PLM, or any other suitable device. In some embodiments, thelaser may generate photons, qubits, or both in the infrared ornear-infrared range (e.g., 1550 nanometers (nm), 980 nm, 900 nm). Forexample, a laser device may be an edge-emitting laser chip having afootprint smaller than one square millimeter and a thickness less than afew micrometers (microns) and comprising a gallium arsenide (GaAs)-basededge-emitting laser, a modulating circuit, and an attenuator ordeflector. Each of the MZIs disclosed herein may comprise a combinationof mirrors, beam splitters, photodetectors fiberoptic cables, lenses,nonlinear crystals, wave plates, motors (e.g., servo motors), motioncontrollers (e.g., servo motor controllers), temperature controllers(e.g., thermoelectric devices), and any other suitable componentsarranged to perform the operations and functions disclosed herein,including, but not limited to, the controlling of optical path length.In some embodiments, a first optoelectronic device may include aparticle source configured to generate single particles (e.g., photonsor electrons) and transmit the generated particles through a double-slitstructure to a first electron detector (e.g., “|1>”) and a secondelectron detector (e.g., “|0>”) as described herein.

The term “security shelf-life” refers to the duration of time (e.g., inyears) that cryptographic keys should be kept secure based on varioussecurity requirements. These security requirements include, but are notlimited to, data retention requirements. For example, in some instancesthe security shelf life of a piece of data may be based on governmentalrisk and regulatory requirements.

The term “control signal” refers to an electronic alert, notification,flag, or control signal configured to instruct, or cause, the PQCsystem, or a QC detection system comprised by or in communication withthe PQC system, to perform an automated process or function without userinteractivity. For example, control signals as described herein maycomprise QC detection alert control signals, leakage alert controlsignals, and tampering alert control signals. In some embodiments, a QCdetection alert control signal may indicate, for example, that aparticular cryptographic technique (e.g., a non-PQC technique, a PQCtechnique, a hybrid PQC technique) used to encrypt or otherwise generateencrypted QC detection data has been compromised by quantum computing.In some embodiments, a leakage alert control signal may indicate, forexample, the existence of a data leakage event associated with QCdetection data stored in an internal data environment that was nevertransmitted outside of that internal data environment. In someembodiments, a tampering alert control signal may indicate, for example,the existence of a data tampering event associated with QC detectiondata, wherein the QC detection data has been altered but signed usingthe same digital signature. In some embodiments, the QC detection alertcontrol signals, leakage alert control signals, tampering alert controlsignals, or a combination thereof may instruct, or cause, the PQC systemto initiate automated analyses and processes to mitigate the quantumcomputing threat within a duration of time. In some instances, the PQCsystem may generate a control signal in accordance with the criteriadiscussed below with reference to Table 3.

The term “quantum computing (QC) detection data” refers to dataconfigured to be used by the PQC system, or a QC detection systemcomprised by or in communication with the PQC system, to detect theexistence and capabilities of quantum computing and, in some instances,the strength of that quantum computing. In some instances, the PQCsystem may comprise fictitious data, such as fictitious account data, afictitious code-signing certificate, any other suitable data, or anycombination thereof. For example, the QC detection data may comprisefictitious financial account data, a fictitious electronic mortgagedocument, a fictitious electronic deed, a fictitious electronic loandocument (e.g., a fictitious auto loan document, a fictitious personalloan document), a fictitious electronic stock transfer agreement,fictitious identity information, fictitious medical data, fictitiouscredit card data, any other suitable data, or any combination thereof.The fictitious identity information may comprise, for example, afictitious name, address, phone number, email address, social securitynumber, driver license number, any other suitable information, or acombination thereof. The fictitious credit card data may comprise, forexample, a fictitious credit card number, credit card issuer (e.g.,financial institution), cardholder name, cardholder billing address,expiration date, CVV security code, credit card network (e.g., Visa,MasterCard, American Express), EMV (originally Europay, Mastercard, andVisa) chip data, magnetic stripe data, etc.), any other suitableinformation, or a combination thereof. In another example, the QCdetection data may comprise a fictitious code-signing certificate, afictitious email certificate, a fictitious legally binding electronicsignature certificate that represents the digital identity of a signer(e.g., a digital identification (ID) certificate, such as an X.509certificate), any other suitable information, or a combination thereof.

The term “data environment” refers to internal data environments,external data environments, hybrid data environments, any other suitableenvironment, or any combination thereof. The internal data environmentsmay comprise, for example, internal information systems, internal datanetworks, internal data storage devices, any other suitable dataenvironment, or any combination thereof. The external data environmentsmay comprise, for example, content delivery networks (CDNs), cloudservice platforms, social media platforms, dark websites, any othersuitable data environment, or any combination thereof. For example, theexternal data environments may comprise a set of websites, such as a setof social media platforms, public websites (e.g., document leakswebsites), online repositories (e.g., online file storage andsynchronization services, online file hosting services), P2P filesharing networks (e.g., BitTorrent), deep websites, dark websites (e.g.,onion addresses that end in the top level domain “.onion”), the MortgageElectronic Registration System (MERS), CDNs (including, but not limitedto, meta-CDNs), cloud service platforms, any other suitable dataenvironment, or any combination thereof.

The term “non-PQC technique” refers to a cryptographic technique that isnot resistant to cryptanalytic algorithms implemented on a quantumcomputer. The terms non-PQC technique, classical cryptographictechnique, and modern cryptographic technique are used interchangeablyherein. Non-PQC techniques may comprise, for example, RSA, DH, and othersuch non-PQC cryptographic algorithms. In some instances, a non-PQCtechnique may be a variant of a non-PQC cryptographic algorithm. Forexample, a first non-PQC technique may be RSA-2048, a second non-PQCtechnique may be RSA-3072, and a third non-PQC technique may beRSA-4096, each of which is a different variant of the same non-PQCcryptographic algorithm (e.g., RSA). In another example, a first non-PQCtechnique may be AES-128, and a second non-PQC technique may be DH-2048,each of which is a variant of a different non-PQC cryptographicalgorithm (e.g., AES, DH). In yet another example, a first non-PQCtechnique may encrypt overhead data based on RSA-2048 and transmit theencrypted data over a non-PQC communications channel (e.g., an in-bandcommunications channel), and a second non-PQC technique may transmitoverhead data over a non-PQC communications channel as clear text, eachof which is a different variant of a non-PQC communicationschannel-based cryptographic technique.

The term “PQC technique” refers to a cryptographic technique that isresistant to cryptanalytic algorithms implemented on a quantum computer.Generally, the families of PQC techniques include key management andsignature. PQC techniques may comprise, for example, hash-based PQCtechniques, lattice-based PQC techniques, isogeny-based PQC techniques,code-based PQC techniques, multivariate-based PQC techniques,zero-knowledge proof PQC techniques, PQC communications channel-basedcryptographic techniques, and other suitable techniques. In someinstances, a PQC technique may be a variant of a PQC cryptographicalgorithm. For example, a first PQC technique may be Dilithium II, asecond PQC technique may be Dilithium II, and a third PQC technique maybe Dilithium 128, each of which is a different variant of the same PQCcryptographic algorithm (e.g., Dilithium). In another example, a firstPQC technique may be LUKE, and a second PQC technique may be DilithiumII, each of which is a variant of a different PQC cryptographicalgorithm (e.g., NewHope, Dilithium). In yet another example, a firstPQC technique may encrypt payload data based on Dilithium II andtransmit the encrypted data over a PQC communications channel (e.g., aPQC back channel), and a second PQC technique may generate a secret keythat is used to encrypt payload data based on AES-256 and transmit theencrypted data over a PQC communications channel, each of which is adifferent variant of a PQC communications channel-based cryptographictechnique.

The term “hybrid PQC technique” refers to a cryptographic technique thatcomprises a non-PQC technique and a PQC technique. For example, a hybridPQC technique may comprise a PQC technique and non-PQC techniquecoexisting in a data envelope, as defined by the statement “hybrid PQCtechnique={PQC technique, Non-PQC technique}.” In some embodiments, ahybrid PQC technique may comprise a hybrid PQC cryptographic mode, suchas a signature-based hybrid PQC cryptographic mode consisting of anon-PQC cryptographic signature and a PQC cryptographic signature. Insome embodiments, the hybrid PQC cryptographic mode is valid only ifboth the non-PQC cryptographic signature and the PQC cryptographicsignature are valid. For example, the PQC system may (i) validate thenon-PQC cryptographic signature according to the Federal InformationProcessing Standard (FIPS) publication 140 (e.g., 140-1, 140-2, 140-3);and (ii) validate the PQC cryptographic signature using multiplepublic-key algorithms for X.509 certificates, such as quantum-resistantX.509 Multiple Public Key Algorithm Certificates.

The term “quantum cryptographic technique” refers to a quantumparticle-based cryptographic technique. Quantum cryptographic techniquesmay comprise, for example, quantum key distribution (QKD) techniques,quantum coin flipping protocols, quantum commitment protocols, quantumoblivious transfer protocols, and other suitable techniques. In someinstances, a quantum cryptographic technique may be a variant of aquantum cryptographic algorithm. For example, a first quantumcryptographic technique may be a BB84-based QKD technique, a secondquantum cryptographic technique may be an E91-based QKD technique, and athird quantum cryptographic technique may be a KMB09-based QKDtechnique, each of which is a different variant of the same quantumcryptographic algorithm (e.g., QKD).

The term “non-PQC communications channel” refers to a communicationschannel (e.g., a wired or wireless communications channel) over whichnon-quantum data and signals are exchanged using one or more non-PQCtechniques that do not themselves directly rely on quantum properties.For example, the PQC system described herein may implement a non-PQCcommunications channel by encrypting data based on a non-PQC technique(e.g., RSA) and then transmitting the encrypted data over a non-PQCcommunications channel (e.g., an “in-band” communications channel) or,in some instances, by transmitting unencrypted, clear text data over thenon-PQC communications channel. In some embodiments, a non-PQCcommunications channel may be a classical communications channel derivedfrom a shared secret that is derived using a non-PQC technique, such asa shared secret generated using DH.

The term “PQC communications channel” refers to a communications channel(e.g., a wired or wireless communications channel) over whichnon-quantum data and signals are exchanged using one or more PQCtechniques (e.g., for authentication, encryption, or both) that do notthemselves directly rely on quantum properties. For example, the PQCsystem described herein may implement a PQC communications channel byencrypting data based on a PQC technique (e.g., Dilithium II) and thentransmitting the encrypted data over a classical back channel (e.g., an“out-of-band” communications channel). In some embodiments, a PQCcommunications channel may be based on an underlying Key EncapsulationMechanism or Key Agreement Scheme. In some embodiments, a PQCcommunications channel may use a Key Encapsulation Mechanism (e.g.,SIKE, NTRUPrime, Kyber) to encapsulate a shared secret and ensure itssafe transmission between Alice and Bob. This shared secret subsequentlywill either (i) be used as a Symmetric Key (e.g., for Symmetric Keyencryption) or (ii) be handed over to a Key Derivation Function togenerate a shared encryption key. In some embodiments, a PQCcommunications channel may use a Key Agreement Scheme (e.g., SIDH,NewHopeDH) may allow both Alice and Bob to calculate the shared secretbased on public parameters and public key that they exchange. Unlike KeyEncapsulation Mechanisms, Key Agreement Schemes do not encapsulate thecalculated shared secret with ciphertext. Key Agreement Schemes may beextended to generate Ephemeral keys. In some instances, after the sharedsecret is calculated, the keys are destroyed to preserve perfect forwardsecrecy. In some embodiments, a PQC communications channel may be aclassical communications channel derived from a shared secret that isderived using a Key Encapsulation Mechanism or a Key Agreement Scheme.

The term “quantum communications channel” refers to a quantumcommunications channel (e.g., an optical line, a quantum line) overwhich quantum data and particles, such as qubits, are exchanged usingone or more quantum cryptographic techniques (e.g., QKD) that directlyrely on quantum properties, such as quantum uncertainty, quantumentanglement, or both.

Having set forth a series of definitions called-upon throughout thisapplication, an example system architecture is described below forimplementing example embodiments and features of the present disclosure.

System Architecture

Methods, systems, apparatuses, and computer program products of thepresent disclosure may be embodied by any of a variety of devices. Forexample, the method, system, apparatus, and computer program product ofan example embodiment may be embodied by one or more networked devices,such as one or more servers, remote servers, cloud-based servers (e.g.,cloud utilities), or other network entities, and configured tocommunicate with one or more devices, such as one or more serverdevices, client devices, database server devices, remote server devices,external data repositories, other suitable devices, or a combinationthereof.

In some instances, the method, system, apparatus, and computer programproduct of an example embodiment may be embodied by one or more quantumcommunications circuitries, such as one or more quantum particleencoders, quantum particle decoders, laser devices, quantum lines,quantum particle storage devices, other suitable quantum communicationsdevices or components, or a combination thereof.

Example embodiments of the client devices include any of a variety ofstationary or mobile computing devices, such as a mobile telephone,smartphone, smartwatch, smart speaker, portable digital assistant (PDA),tablet computer, laptop computer, desktop computer, kiosk computer,automated teller machine (ATM), point of sale terminal (POS), electronicworkstation, any other suitable computing device, or any combination ofthe aforementioned devices.

FIG. 1 illustrates a system diagram of a set of devices that may beinvolved in some example embodiments described herein. In this regard,FIG. 1 discloses an example environment 100 within which embodiments ofthe present disclosure may operate to provide various PQC operations. Asillustrated, a PQC system 102 may be connected to one or more PQC serverdevices 104 in communication with one or more PQC databases 106. The PQCsystem 102 may be connected to one or more server devices 110A-110N, oneor more client devices 112A-112N, one or more database server devices114, one or more remote server devices 116, and/or one or more externaldata repositories 120 through one or more communications networks 108.One or more communications networks 108 may include any suitable networkor combination of networks, such as a virtual network, the Internet, alocal area network (LAN), a Wi-Fi network, a Worldwide Interoperabilityfor Microwave Access (WiMAX) network, a home network, a cellularnetwork, a near field communications (NFC) network, other types ofnetworks, or a combination thereof. In some embodiments, the PQC system102 may be configured to provide PQC and monitor changes therein asdescribed in further detail below.

The PQC system 102 may be embodied as one or more specializedcircuitries, computers, or computing systems and may comprise one ormore PQC server devices 104 and one or more PQC databases 106. The oneor more PQC server devices 104 may be embodied as one or more servers,remote servers, cloud-based servers (e.g., cloud utilities), processors,any other suitable server devices, or any combination thereof. The oneor more PQC server devices 104 may be configured to receive, process,generate, and transmit data, signals, and electronic information tofacilitate the operations of the PQC system 102. The one or more PQCdatabases 106 may be embodied as one or more data storage devices, suchas Network Attached Storage (NAS) devices or separate databases orservers. The one or more PQC databases 106 may be configured to storeand provide access to data and information used by the PQC system 102 tofacilitate the operations of the PQC system 102. For example, the one ormore PQC databases 106 may store user account credentials for users ofone or more server devices 110A-110N, one or more client devices112A-112N, one or more database server devices 114, one or more remoteserver devices 116, or a combination thereof. In another example, theone or more PQC databases 106 may store data regarding devicecharacteristics for the one or more server devices 110A-110N, one ormore client devices 112A-112N, one or more database server devices 114,one or more remote server devices 116, or a combination thereof. Invarious embodiments, one or more PQC systems 102, one or more PQC serverdevices 104, one or more PQC databases 106, one or more server devices112A-112N, one or more client devices 112A-112N may be configured and/orprogrammed to generate blockchains and corresponding side chains;provide blockchains and corresponding side chains for storage by anexternal data repository 120, and/or the like.

In some embodiments, the one or more PQC server devices 104, the one ormore PQC databases 106, or both may include or store various data andelectronic information associated with one or more data, dataattributes, data envelopes, enveloped data structures, policyinformation, policy attributes, risk profile data structures, QCdetection data, QC detection techniques (including, but not limited to,detection of quantum computing capabilities; data leakage detectiontechniques; and data tampering detection techniques), QC detection alertcontrol signals, non-PQC techniques, non-PQC cryptographic performanceinformation, non-PQC attributes, PQC performance information, PQCtechniques, PQC attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, graphical userinterface (GUI) data, any other suitable data or electronic information,any links or pointers thereto, or combinations thereof. In someembodiments, the one or more PQC server devices 104, the one or more PQCdatabases 106, or both may include or store various quantum information,such as one or more quantum particles (e.g., pairs of entangled quantumparticles, one entangled quantum particle in a pair of entangled quantumparticles), quantum cryptographic keys, quantum one-time pads, any othersuitable quantum information, any links or pointers thereto, orcombinations thereof.

The one or more server devices 110A-110N may be embodied by one or morecomputing devices. In some embodiments, the one or more server devices110A-110N may be embodied as one or more servers, remote servers,cloud-based servers (e.g., cloud utilities), processors, or any othersuitable devices, or any combination thereof. In some embodiments, theone or more server devices 110A-110N may receive, process, generate, andtransmit data, signals, and electronic information to facilitate theoperations of the PQC system 102. Information received by the PQC system102 from one or more server devices 110A-110N may be provided in variousforms and via various methods. In some embodiments, the one or moreserver devices 110A-110N may include or store various data andelectronic information associated with one or more data, dataattributes, data envelopes, enveloped data structures, policyinformation, policy attributes, risk profile data structures, QCdetection data, QC detection techniques, QC detection alert controlsignals, non-PQC techniques, non-PQC cryptographic performanceinformation, non-PQC attributes, PQC performance information, PQCtechniques, PQC attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, GUI data, any othersuitable data or electronic information, any links or pointers thereto,or combinations thereof. In some embodiments, the one or more serverdevices 110A-110N may include or store various quantum information, suchas one or more quantum particles (e.g., pairs of entangled quantumparticles, one entangled quantum particle in a pair of entangled quantumparticles), quantum cryptographic keys, quantum one-time pads, any othersuitable quantum information, any links or pointers thereto, orcombinations thereof.

The one or more client devices 112A-112N may be embodied by one or morecomputing devices. Information received by the PQC system 102 from theone or more client devices 112A-112N may be provided in various formsand via various methods. For example, the one or more client devices112A-112N may be smartphones, laptop computers, netbooks, tabletcomputers, wearable devices, desktop computers, automated tellermachines (ATMs), point-of-sale terminals (POS), electronic workstations,or the like, and the information may be provided through various modesof data transmission provided by these client devices. In someembodiments, the one or more client devices 112A-112N may include orstore various data and electronic information associated with one ormore users. For example, the one or more client devices 112A-112N mayinclude or store user information (including, but not limited to, userprofile information), any other suitable data, or any combinationthereof. In some embodiments, the one or more client devices 112A-112Nmay include or store various data and electronic information associatedwith one or more data, data attributes, data envelopes, enveloped datastructures, policy information, policy attributes, risk profile datastructures, QC detection data, QC detection techniques, QC detectionalert control signals, non-PQC techniques, non-PQC performanceinformation, non-PQC attributes, PQC performance information, PQCtechniques, PQC attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, GUI data, any othersuitable data or electronic information, any links or pointers thereto,or combinations thereof. In some embodiments, the one or more clientdevices 112A-112N may include or store various quantum information, suchas one or more quantum particles (e.g., pairs of entangled quantumparticles, one entangled quantum particle in a pair of entangled quantumparticles), quantum cryptographic keys, quantum one-time pads, any othersuitable quantum information, any links or pointers thereto, orcombinations thereof.

In embodiments where a client device 112 is a mobile device, such as asmartphone or tablet, the mobile device may execute an “app” (e.g., athin-client application) to interact with the PQC system 102, one ormore server devices 110A-110N, one or more database server devices 114,one or more remote server devices 116, or a combination thereof. Suchapps are typically designed to execute on mobile devices, such astablets or smartphones. For example, an app may be provided thatexecutes on mobile device operating systems such as Apple Inc.'s iOS,Google LLC's Android®, or Microsoft Corporation's Windows®. Theseplatforms typically provide frameworks that allow apps to communicatewith one another and with particular hardware and software components ofmobile devices. For example, the mobile operating systems named aboveeach provide frameworks for interacting with camera circuitry,microphone circuitry, sensor circuitry, location services circuitry,wired and wireless network interfaces, user contacts, and otherapplications in a manner that allows for improved interactions betweenapps while also preserving the privacy and security of individual users.In some embodiments, a mobile operating system may also provide forimproved communication interfaces for interacting with external devices(e.g., server devices, client devices, database server devices, remoteserver devices). Communication with hardware and software modulesexecuting outside of the app is typically provided via APIs provided bythe mobile device operating system.

The one or more database server devices 114 may be embodied by one ormore computing devices, server devices, servers, data storage devices,databases, or a combination thereof. In some embodiments, the one ormore database server devices 114 may be embodied as one or more datastorage devices, such as one or more NAS devices, or as one or moreseparate databases or database servers. In some embodiments, the one ormore database server devices 114 may be embodied as one or more servers,remote servers, cloud-based servers (e.g., cloud utilities), processors,or any other suitable devices, or any combination thereof. In someembodiments, the one or more database server devices 114 may receive,process, generate, and transmit data, signals, and electronicinformation to facilitate the operations of the PQC system 102.Information received by the PQC system 102 from one or more databaseserver devices 114 may be provided in various forms and via variousmethods. It will be understood, however, that in some embodiments, theone or more database server devices 114 need not themselves be databasesor database servers but may be peripheral devices communicativelycoupled to databases or database servers.

In some embodiments, the one or more database server devices 114 mayinclude or store various data and electronic information associated withone or more data, data attributes, data envelopes, enveloped datastructures, policy information, policy attributes, risk profile datastructures, QC detection data, QC detection techniques, QC detectionalert control signals, non-PQC techniques, non-PQC performanceinformation, non-PQC attributes, PQC performance information, PQCtechniques, PQC attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, GUI data, any othersuitable data or electronic information, any links or pointers thereto,or combinations thereof. In some embodiments, the one or more databaseserver devices 114 may include or store exogenous data. The exogenousdata may comprise, for example, public sentiment data structures (e.g.,a widespread data breach at a third-party system, such as a merchant; astock market crash; a geopolitical event), news articles, FDIC data,NIST data, company intranet data, technological advancements, scientificpublications, financial data (e.g., stock market data, commodity marketdata, money market data), legal data (e.g., lawsuit data, regulatorydata), any other suitable exogenous data, or any combination thereof. Insome embodiments, the one or more database server devices 114 mayinclude or store various quantum information, such as one or morequantum particles (e.g., pairs of entangled quantum particles, oneentangled quantum particle in a pair of entangled quantum particles),quantum cryptographic keys, quantum one-time pads, any other suitablequantum information, any links or pointers thereto, or combinationsthereof.

The one or more remote server devices 116 may be embodied by one or morecomputing devices, server devices, servers, data storage devices,databases, or a combination thereof. In some embodiments, the one ormore remote server devices 116 may be embodied as one or more datastorage devices, such as one or more NAS devices, or as one or moreseparate databases or database servers. In some embodiments, the one ormore remote server devices 116 may be embodied as one or more servers,remote servers, cloud-based servers (e.g., cloud utilities), processors,or any other suitable devices, or any combination thereof. In someembodiments, the one or more remote server devices 116 may receive,process, generate, and transmit data, signals, and electronicinformation to facilitate the operations of the PQC system 102.Information received by the PQC system 102 from one or more remoteserver devices 116 may be provided in various forms and via variousmethods. It will be understood, however, that in some embodiments, theone or more remote server devices 116 need not themselves be servers butmay be peripheral devices communicatively coupled to servers.

In some embodiments, the one or more remote server devices 116 mayinclude or store various data and electronic information associated withone or more data, data attributes, data envelopes, enveloped datastructures, policy information, policy attributes, risk profile datastructures, QC detection data, QC detection techniques, QC detectionalert control signals, non-PQC techniques, non-PQC performanceinformation, non-PQC attributes, PQC performance information, PQCtechniques, PQC attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, GUI data, exogenousdata, any other suitable data or electronic information, any links orpointers thereto, or combinations thereof. In some embodiments, the oneor more remote server devices 116 may include or store various quantuminformation, such as one or more quantum particles (e.g., pairs ofentangled quantum particles, one entangled quantum particle in a pair ofentangled quantum particles), quantum cryptographic keys, quantumone-time pads, any other suitable quantum information, any links orpointers thereto, or combinations thereof.

The one or more external database repositories 120 may be embodied byone or more computing devices, server devices, servers, data storagedevices, databases, or a combination thereof. In various embodiments, anexternal data repository 120 is operated by and/or on behalf of adifferent entity that the PQC system 102. For example, the external datarepository 120 may be Cloud-based storage system and/or other thirdparty storage system. In some embodiments, the one or more externaldatabase repositories 120 may be embodied as one or more data storagedevices, such as one or more NAS devices, or as one or more separatedatabases or database servers. In some embodiments, the one or moreexternal database repositories 120 may be embodied as one or moreservers, remote servers, cloud-based servers (e.g., cloud utilities),processors, or any other suitable devices, or any combination thereof.In some embodiments, the one or more external database repositories 120may receive, process, generate, and transmit data, signals, andelectronic information to facilitate the operations of the PQC system102. Information received by the PQC system 102 from one or moreexternal database repositories 120 may be provided in various forms andvia various methods. It will be understood, however, that in someembodiments, the one or more external database repositories 120 need notthemselves be databases or database servers but may be peripheraldevices communicatively coupled to databases or database servers.

In some embodiments, the one or more external database repositories 120may include or store various data and electronic information associatedwith one or more data, data attributes, data envelopes, enveloped datastructures, policy information, policy attributes, risk profile datastructures, QC detection data, QC detection techniques, QC detectionalert control signals, non-PQC techniques, non-PQC performanceinformation, non-PQC attributes, PQC performance information, PQCtechniques, PQC attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, GUI data, blockchainsand corresponding side chains, any other suitable data or electronicinformation, any links or pointers thereto, or combinations thereof.

In some embodiments, the one or more server devices 110A-110N, the oneor more client devices 112A-112N, the one or more database serverdevices 114, the one or more remote server devices 116, the one or moreexternal data repositories 120, or any combination thereof may interactwith the PQC system 102 (and/or one another) over one or morecommunications networks 108. As yet another example, the one or moreserver devices 110A-110N, the one or more client devices 112A-112N, theone or more database server devices 114, the one or more remote serverdevices 116, the one or more external data repositories or a combinationthereof may include various hardware or firmware designed to interfacewith the PQC system 102. For example, an example server device 110A maybe a session authentication server modified to communicate with the PQCsystem 102, and another example server device 110B may be apurpose-built session authentication server offered for the primarypurpose of communicating with the PQC system 102. As another example, anexample client device 112A may be a user's smartphone and may have anapplication stored thereon facilitating communication with the PQCsystem 102, whereas another example client device 112B may be apurpose-built device offered for the primary purpose of communicatingwith the PQC system 102.

In some embodiments, the one or more server devices 110A-110N, the oneor more client devices 112A-112N, the one or more database serverdevices 114, the one or more remote server devices 116, the one or moreexternal data repositories 120, or any combination thereof may interactwith the PQC system 102 over one or more PQC communications channels.The PQC communications channel may be, for example, a communicationschannel over which data is transmitted and received using a PQCtechnique, such as a PQC back channel (e.g., a PQC out-of-bandcommunications channel). In some embodiments, the PQC system 102 mayupgrade the application software in a server device 110, client device112, database server device 114, or remote server device 116 so that theupgraded application software is configured to recognize a PQCcommunications channel and allow communication with the PQC system 102over the PQC communications channel. In some embodiments, where a serverdevice 110, client device 112, database server device 114, or remoteserver device 116 is a non-PQC device (e.g., a computing device that isnot configured to interact with, or capable of interacting with, the PQCsystem 102 over a PQC communications channel), that non-PQC device mayinteract with the PQC system 102 over a PQC communications channel usinga PQC shim or PQC add-on device configured to allow communication withthe PQC system 102 over the PQC communications channel. In one example,the PQC system 102 may determine that a server device 110, client device112, database server device 114, or remote server device 116 is anon-PQC device and transmit a PQC shim to that non-PQC device forinstallation (e.g., automatic installation, manual installation) in theprotocol stack of that device. The PQC shim may be embodied as, forexample, computer program instructions (e.g., software, firmware). Inanother example where the server device 110, client device 112, databaseserver device 114, or remote server device 116 is a non-PQC device, aPQC add-on device may be communicatively coupled to the non-PQC device.The PQC add-on device may be embodied as, for example, a PQC peripheraldevice communicatively coupled (e.g., via a wired communications path,wireless communications path, or both) to the non-PQC device.Additionally, or alternatively, the PQC add-on device may be embodiedas, for example, a PQC application specific integrated circuit (ASIC)installed within a housing of the non-PQC device, or any other suitabledevice or circuitry. In some embodiments, the PQC shim may comprise aset of routines with network capability and a PQC endpoint.

Example Implementing Apparatuses

The PQC system 102 described with reference to FIG. 1 may be embodied byone or more computing systems, such as apparatus 200 shown in FIG. 2A,apparatus 280 shown in FIG. 2B, and apparatus 290 shown in FIG. 2C. Insome embodiments, apparatus 200 shown in FIG. 2A may represent anexample PQC system 102, a PQC server device 104, a PQC database, or acombination thereof. In some embodiments, apparatus 280 shown in FIG. 2Bmay represent an example server device 110, client device 112, databaseserver device 114, remote server device 116, any other suitable device,or a combination thereof. In some embodiments, apparatus 290 shown inFIG. 2C may represent an example PQC add-on device configured to becommunicatively coupled to a server device 110, client device 112,database server device 114, remote server device 116, any other suitabledevice, or a combination thereof.

FIG. 2A illustrates an example apparatus 200 that may be and/or be partof a PQC system 102 in an example embodiment. As illustrated in FIG. 2A,the apparatus 200 may include one or more of processing circuitry 202,memory 204, input-output circuitry 206, PQC callback circuitry 207,communications circuitry 208 (including, but not limited to, classicalcommunications circuitry 210 and quantum communications circuitry 212),data envelope generation circuitry 216, data structure generationcircuitry 218, data monitoring circuitry 220 (including, but not limitedto, data access monitoring circuitry 222 and data zone monitoringcircuitry 224), cryptographic circuitry 248 (including, but not limitedto, non-PQC cryptographic circuitry 250 and PQC cryptographic circuitry252), machine learning circuitry 254, data storage circuitry 256, userinterface (UI) circuitry 258, any other suitable circuitry, or anycombination thereof. The apparatus 200 may be configured to execute theoperations described above with respect to FIG. 1 and below with respectto FIGS. 4-6C.

In some embodiments, the processing circuitry 202 (and/or co-processoror any other processing circuitry assisting or otherwise associated withthe processor) may be in communication with the memory 204 via a bus forpassing information among components of the apparatus 200. The memory204 may be non-transitory and may include, for example, one or morevolatile and/or non-volatile memories. For example, the memory may be anelectronic storage device (e.g., a computer readable storage medium).The memory 204 may be configured to store information, data, datastructures, content, control signals, applications, instructions, or thelike, for enabling the apparatus to carry out various functions inaccordance with example embodiments of the present disclosure. In someinstances, the memory 204 may be configured to store data, datastructures, data elements, and electronic information associated withone or more data (e.g., unencrypted data, encrypted data, decrypteddata, re-encrypted data, double encrypted data, data access controlinformation, bitstreams of data, QC detection data, links or pointersthereto), data attributes, data envelopes, enveloped data structures,policy information, policy attributes, risk profile data structures, QCdetection techniques (including, but not limited to, detection ofquantum computing capabilities; data leakage detection techniques; anddata tampering detection techniques), control signals (e.g., QCdetection alert control signals), non-PQC techniques, non-PQCperformance information, non-PQC attributes, PQC performanceinformation, PQC techniques, PQC attributes, symmetric cryptographickeys, asymmetric cryptographic keys, any other suitable data orelectronic information, or combinations thereof. It will be understoodthat the memory 204 may be configured to store any data, datastructures, electronic information, requests, control signals,embodiments, examples, figures, techniques, processes, operations,methods, systems, apparatuses, or computer program products describedherein, or any combination thereof.

The processing circuitry 202 may be embodied in a number of differentways and may, for example, include one or more processing devicesconfigured to perform independently. Additionally, or alternatively, theprocessing circuitry 202 may include one or more processors configuredin tandem via a bus to enable independent execution of instructions,pipelining, multithreading, or a combination thereof. The use of theterm “processing circuitry” may be understood to include a single coreprocessor, a multi-core processor, multiple processors internal to theapparatus, remote or “cloud” processors, or a combination thereof.

In an example embodiment, the processing circuitry 202 may be configuredto execute instructions stored in the memory 204 or otherwise accessibleto the processor. Alternatively, or additionally, the processingcircuitry 202 may be configured to execute hard-coded functionality. Assuch, whether configured by hardware or software methods, or by acombination of hardware with software, the processor may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present disclosure whileconfigured accordingly. As another example, when the processor isembodied as an executor of software instructions, the instructions mayspecifically configure the processor to perform the functionalities andoperations described herein when the instructions are executed. Forexample, the processing circuitry 202 may be configured to executeinstructions stored in the memory 204 or otherwise accessible to theprocessing circuitry, possibly in cooperation with various othercircuitry, to generate a blockchain and corresponding side chains,provide a blockchain and corresponding side chains for storage by anexternal data repository 120, provide information/data to be included ina blockchain and/or corresponding side chains by an external datarepository 120, or a combination thereof.

In some embodiments, the apparatus 200 may include input-outputcircuitry 206 that may, in turn, be in communication with processingcircuitry 202 to provide output to the user and, in some embodiments, toreceive an indication of a user input such as a command provided by auser. The input-output circuitry 206 may comprise a user interface(e.g., a user interface generated by user interface circuitry includedin the apparatus 200) comprising a display that may include a web userinterface, a mobile application, a client device, a display device, adisplay screen, or any other suitable hardware or software. In someembodiments, the input-output circuitry 206 may also include a keyboard,a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input-output mechanisms. The processingcircuitry 202, the input-output circuitry 206 (which may utilize theprocessing circuitry 202), or both may be configured to control one ormore functions of one or more user interface elements through computerprogram instructions (e.g., software, firmware) stored on a memory(e.g., memory 204). Input-output circuitry 206 is optional and, in someembodiments, the apparatus 200 may not include input-output circuitry.For example, where the apparatus 200 does not interact directly with theuser, the apparatus 200 may be configured to generate (e.g., by UIcircuitry 258) user interface data (e.g., data attribute GUI data, riskprofile GUI data, PQC optimization GUI data, data monitoring GUI data)for display by one or more other devices with which one or more usersdirectly interact and transmit the generated user interface data to oneor more of those devices.

In some embodiments, the apparatus 200 may include PQC callbackcircuitry 207 that includes hardware components designed or configuredto provide for communication with: the PQC cryptographic circuitry(e.g., PQC cryptographic circuitry 252 shown in FIG. 2B) of a clientdevice (e.g., apparatus 280 shown in FIG. 2B, wherein the apparatus 280does not include the PQC shim circuitry 260); a PQC shim (e.g., PQC shimcircuitry 260 shown in FIG. 2B) installed in a network layer of a clientdevice (e.g., apparatus 280 shown in FIG. 2B, wherein the apparatus 280includes the PQC shim circuitry 260, and wherein the PQC shim circuitry260 comprises the PQC cryptographic circuitry 252); a PQC add-on device(e.g., the apparatus 290 shown in FIG. 2C) communicatively coupled to aclient device (e.g., apparatus 280 shown in FIG. 2B, wherein theapparatus 280 does not include the PQC cryptographic circuitry 252 orthe PQC shim circuitry 260); any other suitable circuitry or device; orany combination thereof. For example, PQC callback circuitry 207 may beconfigured to provide PQC communications channel-based cryptographictechniques, such as the transmission and receipt of sensitive portions(e.g., payloads) of electronic communications to a PQC shim or a PQCadd-on device over one or more PQC communications channels.

In some embodiments, the PQC callback circuitry 207 may be configured toestablish a non-PQC communications channel based on one or more non-PQCcryptographic algorithms (e.g., as provided by non-PQC cryptographiccircuitry 250). In some embodiments, the PQC callback circuitry 207 maybe configured to establish a PQC communications channel based on one ormore PQC cryptographic algorithms (e.g., as provided by PQCcryptographic circuitry 252). In some embodiments, the PQC callbackcircuitry 207 may be configured to establish a hybrid PQC communicationschannel based on one or more hybrid PQC cryptographic algorithms (e.g.,as provided by cryptographic circuitry 248, such as provided by acombination of non-PQC cryptographic circuitry 250 and PQC cryptographiccircuitry 252).

In one illustrative example, the PQC callback circuitry 207 may beconfigured to establish a PQC communications channel using a PQCcryptographic algorithm. The cryptographic circuitry 248 may be furtherconfigured to generate a secret key (e.g., an AES symmetriccryptographic key). Thereafter, the PQC callback circuitry 207 maytransmit the secret key to a remote device (e.g., apparatus 280,apparatus 290) over the PQC communications channel for use in thesubsequent exchange of encrypted communications.

In some embodiments, the PQC callback circuitry 207 may be configured togenerate (e.g., dynamically generate) the PQC communications channelbased on a set of data attributes about the electronic communication, arisk profile data structure indicative of a vulnerability of theelectronic communication in a PQC data environment, and PQC performanceinformation associated with a set of PQC techniques, wherein the PQCperformance information comprises a set of PQC performance attributesfor each PQC technique in the set of PQC techniques. In someembodiments, the PQC callback circuitry 207 may be configured togenerate the PQC communications channel based on a machine learningtechnique, such as a machine learning technique provided or performed bythe machine learning circuitry 254.

The communications circuitry 208 may be any device or circuitry embodiedin either hardware or a combination of hardware and software that isconfigured to receive and/or transmit classical data, quantuminformation, or both from or to a network and/or any other device,circuitry, or module in communication with the apparatus 200. In thisregard, the communications circuitry 208 may include, for example,classical communications circuitry 210 and quantum communicationscircuitry 212.

The classical communications circuitry 210 may be any device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from or to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 200. In this regard, the classical communicationscircuitry 210 may include, for example, a network interface for enablingcommunications with a wired or wireless communications network. Forexample, the classical communications circuitry 210 may include one ormore network interface cards, antennae, buses, switches, routers,modems, and supporting hardware and/or software, or any other devicesuitable for enabling communications via a network. In some embodiments,the communication interface may include the circuitry for interactingwith the antenna(s) to cause transmission of signals via the antenna(s)or to handle receipt of signals received via the antenna(s). Thesesignals may be transmitted by the apparatus 200 using any of a number ofwireless personal area network (PAN) technologies, such as Bluetooth®v1.0 through v5.0, Bluetooth Low Energy (BLE), infrared wireless (e.g.,IrDA), ultra-wideband (UWB), induction wireless transmission, or anyother suitable technologies. In addition, it should be understood thatthese signals may be transmitted using Wi-Fi, NFC, WiMAX or otherproximity-based communications protocols.

The quantum communications circuitry 212 may be any device or circuitryembodied in either hardware or a combination of hardware and softwarethat is configured to receive and/or transmit quantum particles, such asphotons, electrons, or both from or to any other device, circuitry, ormodule in communication with the apparatus 200. In this regard, thequantum communications circuitry 212 may include, for example, opticalcomponents such as an optical communications interface for enablingoptical communications over a quantum line. In some embodiments, thequantum communications circuitry 212 may include encoding circuitry(e.g. an on-chip encoder) to generate a set of entangled quantumparticles (e.g., qubits, qutrits, qudits) and decoding circuitry (e.g.,an on-chip decoder) to receive (e.g., directly or indirectly, such asvia switching circuitry), store, and measure a set of entangled quantumparticles. In some embodiments, the quantum communications circuitry 212may further include quantum basis determination circuitry configured todetermine the quantum bases, or sets of quantum bases, for encoding anddecoding of a given set of quantum particles. In some embodiments, thequantum communications circuitry 212 may include or be communicativelycoupled to one or more quantum storage devices configured to storevarious quantum information, such as one or more quantum particles(e.g., pairs of entangled quantum particles, one entangled quantumparticle in a pair of entangled quantum particles), quantumcryptographic keys, quantum one-time pads, any other suitable quantuminformation, any links or pointers thereto, and combinations thereof.

In some embodiments, the first portion of the electronic communicationmay comprise a PQC indicator data structure that identifies the PQCcommunications channel and indicates that the second portion of theelectronic communication is to be transmitted over the PQCcommunications channel. In some embodiments, the PQC indicator datastructure may comprise a link to a PQC shim configured to allowcommunication with the PQC callback circuitry 207 over the PQCcommunications channel. For example, the PQC indicator data structuremay comprise a PQC shim automatic installation control signal indicativeof an electronic instruction for the client device (e.g., apparatus 280shown in FIG. 2B) to automatically install the PQC shim based on thelink. In another example, the PQC indicator data structure may comprisea PQC shim manual installation control signal indicative of anelectronic instruction for the client device to manually install the PQCshim based on the link. In still another example, the first portion ofthe electronic communication may comprise a PQC smart contractcomprising the PQC indicator data structure. Once installed on theclient device, the PQC shim may be implemented as PQC shim circuitry 260shown in FIG. 2B.

In some embodiments, the communications circuitry 208 may be configuredto receive, retrieve, or obtain data. In some embodiments, the data maycomprise data access control information, a link or pointer to the data(e.g., a link to a credit card number), a bitstream, a binary largeobject (BLOB), any other suitable data, or any combination thereof. Insome embodiments, the data may have been encrypted based on a set ofencryption attributes, such as a set of non-PQC attributes, a set of PQCattributes, or both (e.g., double encryption where the data has beenencrypted based on a set of non-PQC attributes and then encrypted againbased on a set of PQC attributes). In some embodiments, thecommunications circuitry 208 may be configured to receive, retrieve, orobtain the data from a data storage device, such as memory 204, one ormore of the one or more PQC databases 106, the one or more databaseserver devices 114 (including, but not limited to, one or more datastorage devices communicatively coupled, either directly or indirectly,to the one or more database server devices 114), the one or more remoteserver devices 116, the one or more server devices 110A-110N, the one ormore client devices 112A-112N, the one or more external datarepositories 120, any other suitable device or circuitry, or acombination thereof.

The data envelope generation circuitry 216 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data envelopegeneration circuitry 216 may be configured to generate a data envelopebased on the set of data attributes. In some embodiments, the dataenvelope generation circuitry 216 may be configured to generate the dataenvelope based on the set of data attributes. In some embodiments, thedata envelope may comprise the set of data attributes. In someembodiments, the data envelope generation circuitry 216 may beconfigured to generate the data envelope based on the set of dataattributes, a risk profile data structure, any other suitable data, orany combination thereof. In some embodiments, the data envelope maycomprise the set of data attributes, a risk profile data structure, anyother suitable data, or any combination thereof. In some embodiments,each piece of data may have a data envelope, wherein the data envelopecomprises one or more attributes about the data. In some embodiments,the data and its envelope may be referred to as a “data BLOB.” In someinstances, the data envelope will keep track of who accessed the data,such as who took an encrypted snapshot of the data and when thatencrypted snapshot was taken. In an example, embodiment, a data envelopegeneration circuitry 216 is configured to bundle an encryptedinformation/data instance and a corresponding decryption algorithm togenerate an encryption bundle.

The data structure generation circuitry 218 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data structuregeneration circuitry 218 may be configured to generate an enveloped datastructure based on the data envelope and the data. In some embodiments,the enveloped data structure comprises the data envelope and the data.In some embodiments, the enveloped data structure comprises the dataenvelope (e.g., set of data attributes, risk profile data structure, anyother suitable data, or any combination thereof) and the data (e.g.,data access control information, link or pointer to the data, bitstream,BLOB, any other suitable data, or any combination thereof). For example,the enveloped data structure may comprise the data enveloped by the dataenvelope.

The data monitoring circuitry 220 includes hardware components designedor configured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the data monitoring circuitry 220 may beconfigured to monitor data, enveloped data structures, any othersuitable data or electronic information, or any combination thereof. Inthis regard, the data monitoring circuitry 220 may include, for example,data access monitoring circuitry 222 and data zone monitoring circuitry224.

In some embodiments, the data monitoring circuitry 220 may be configuredto monitor an enveloped data structure and identify changes in theenveloped data structure. In some embodiments, the enveloped datastructure may comprise a data envelope and data. In some embodiments,the data envelope may comprise a set of data attributes about the dataand a risk profile data structure indicative of a vulnerability of thedata in a PQC data environment. In some embodiments, the data has beenencrypted based on a set of non-PQC attributes or a set of PQCattributes. For example, the data monitoring circuitry 220 may beconfigured to generate an electronic indication of the change in theenveloped data structure, such as a control signal, metadata, or flagindicative of the change. In some embodiments, the data monitoringcircuitry 220 may be configured to automatically monitor the envelopeddata structure in real-time and without user interactivity;automatically identify the change in the enveloped data structure inreal-time and without user interactivity; and generate the electronicindication of the change in the enveloped data structure in real-timeand without user interactivity.

In some embodiments, the change in the enveloped data structure may be achange in the risk profile data structure, such as a change in a valueof the data, a change in a longevity of the data, a change in acryptostrength of the data, a change in a result of a vulnerability scanof the data, a change in a vulnerability score value (e.g., any valueassociated with a vulnerability score data structure comprising avulnerability score range comprising a minimum vulnerability scorevalue, a maximum vulnerability score value, a median vulnerability scorevalue, a mean vulnerability score value, a first quartile vulnerabilityscore value, a third quartile vulnerability score value, aninterquartile vulnerability score range between the first quartilevulnerability score value and the third quartile vulnerability scorevalue, any other suitable value, metric, or range, or any combinationthereof) indicative of a percentage of vulnerability of the data in thePQC data environment, a change in a compliance score value indicative ofa percentage of compliance of the data to a set of compliancerequirements, a change in an approximate time to a quantum computingthreat (e.g., changes in collapse time, changes in vulnerabilities toexisting algorithms, receipt of a QC detection alert control signal), achange in exogenous data associated with the data, wherein the exogenousdata comprises a public sentiment data structure (e.g., a widespreaddata breach at a third-party system, such as a merchant; a stock marketcrash; a geopolitical event), a change in any other suitable data, datastructure, or data element, or any combination thereof. In someembodiments, the change in the enveloped data structure may be adetermination that the data has been accessed and by whom (e.g., user,entity, location). In some embodiments, the change in the enveloped datastructure may be a determination that the data has transitioned to adifferent data zone (e.g., from a first data zone to a second datazone).

In some embodiments, the data monitoring circuitry 220 may be configuredto monitor a set of data environments for electronic information relatedto the encrypted QC detection data. For example, the data monitoringcircuitry 220 may be configured to monitor a set of internal dataenvironments (e.g., internal information systems, internal datanetworks, internal data storage devices) and, in some instances, flaguses of the QC detection data, the private cryptographic key used toencrypt the QC detection data, or any other suitable data that made itsway into the internal data environment. In another example, the datamonitoring circuitry 220 may be configured to monitor a set of externaldata environments (e.g., content delivery networks (CDNs), cloud serviceplatforms, social media platforms, dark websites) and, in someinstances, flag uses of the unencrypted QC detection data or any othersuitable data that made its way into the external data environment.

In some embodiments, the data monitoring circuitry 220 may be furtherconfigured to generate a QC detection alert control signal in responseto detection of the electronic information related to the encrypted QCdetection data. For example, the data monitoring circuitry 220 may befurther configured to generate a QC detection alert control signal whenthe detected electronic information related to the encrypted QCdetection data comprises decrypted QC detection data that is the same asthe QC detection data. In some embodiments, the QC detection alertcontrol signal may indicate, for example, that the cryptographictechnique used to encrypt the QC detection data has been compromised byquantum computing. In some embodiments, the QC detection alert controlsignal may be configured to instruct, or cause, the cryptographiccircuitry 248 to encrypt or re-encrypt data (e.g., enveloped datastructures stored in one or more internal or third-party data storagedevices) using a PQC technique having a cryptostrength that cannot becompromised by that particular quantum computer. In some embodiments,the QC detection alert control signal may be configured to instruct, orcause, the UI circuitry 258 to generate QC detection alert GUI data(e.g., an electronic notification, e-mail, pop-up display, audiblealarm) and transmit the generated QC detection alert GUI data to theinput-output circuitry 206, and the input-output circuitry 206 may beconfigured to receive the QC detection alert GUI data and display thereceived QC detection alert GUI data on one or more display screens.

In some embodiments, wherein the cryptographic circuitry 248 isconfigured to not transmit the encrypted QC detection data, the datamonitoring circuitry 220 may be configured to generate a leakage alertcontrol signal in response to detection of the electronic informationrelated to the encrypted QC detection data. In some embodiments, theleakage alert control signal may indicate, for example, that the QCdetection data was leaked from an internal data environment, when the QCdetection data was leaked from the internal data environment, who leakedthe QC detection data from the internal data environment (e.g., based onthe data lineage of the QC detection data), how the QC detection datawas leaked from the internal data environment, any other suitableinformation, or any combination thereof. In some embodiments, theleakage alert control signal may be configured to instruct, or cause,the communications circuitry 208 to disallow any data to be transmittedout of the internal data environment associated with the leaked QCdetection data. In some embodiments, the leakage alert control signalmay be configured to instruct, or cause, the UI circuitry 258 togenerate leakage alert GUI data (e.g., an electronic notification,e-mail, pop-up display, audible alarm) and transmit the generatedleakage alert GUI data to the input-output circuitry 206, and theinput-output circuitry 206 may be configured to receive the leakagealert GUI data and display the received leakage alert GUI data on one ormore display screens.

In some embodiments, when the detected electronic information related tothe encrypted QC detection data comprises a detected digital signature,the data monitoring circuitry 220 may be further configured to verifythe detected digital signature based on the public cryptographic key. Insome embodiments, the data monitoring circuitry 220 may be furtherconfigured to generate a tampering alert control signal when thedetected electronic information related to the encrypted QC detectiondata further comprises detected payload data that has been digitallysigned based on the detected digital signature, the detected digitalsignature is the same as the QC detection digital signature, and thedetected payload data is different from the QC detection data.

In some embodiments, the tampering alert control signal may indicate,for example, that the QC detection data has been altered but signedusing the same digital signature. For example, the encrypted QCdetection data may comprise QC detection data that has been digitallysigned based on a digital signature (e.g., RSA, such as RSA-PSS; DSA andits elliptic curve variant ECDSA), and the electronic informationrelated to the encrypted QC detection data may comprise payload datathat has been digitally signed based on the digital signature. In someinstances, the payload data may be different from the QC detection data,such as a different fraudulent document digitally signed by the samedigital signature. In some instances, a subset of the payload data maybe the same as a subset of the QC detection data, such as an altereddocument digitally signed by the same digital signature. For example,the QC detection data may comprise a fictitious stock transfer agreementcomprising a first stock transfer attribute indicative of a first amountof transferred shares (e.g., 10 transferred shares), the detectedpayload data may comprise a detected stock transfer agreement comprisinga second stock transfer attribute indicative of a second amount oftransferred shares (e.g., 10,000 transferred shares) different from thefirst amount of transferred shares, and the tampering alert controlsignal may comprise an indication that the fictitious stock transferagreement has been tampered with. In other examples, the detectedpayload data may comprise different buyer or seller information on adigitally signed fictitious electronic mortgage; different ownerinformation on a digitally signed fictitious financial account;different payee or payment amount on a digitally signed fictitiousfinancial transaction (e.g., a fictitious wire transfer, mobile deposit,or electronic check); or any other suitable information.

In some embodiments, the tampering alert control signal may beconfigured to instruct, or cause, the UI circuitry 258 to generatetampering alert GUI data (e.g., an electronic notification, e-mail,pop-up display, audible alarm) and transmit the generated tamperingalert GUI data to the input-output circuitry 206, and the input-outputcircuitry 206 may be configured to receive the tampering alert GUI dataand display the received tampering alert GUI data on one or more displayscreens.

In some embodiments, the data monitoring circuitry 220 includes hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in QC detection. In some embodiments, thedata monitoring circuitry 220 may be configured to monitor QC detectiondata, other data, enveloped data structures, any other suitable data orelectronic information, or any combination thereof.

In some embodiments, the data monitoring circuitry 220 may be configuredto monitor a set of data environments for electronic information relatedto the encrypted QC detection data. For example, the data monitoringcircuitry 220 may be configured to monitor a set of internal dataenvironments (e.g., internal information systems, internal datanetworks, internal data storage devices) and, in some instances, flaguses of the QC detection data, the private cryptographic key used toencrypt the QC detection data, or any other suitable data that made itsway into the internal data environment. In another example, the datamonitoring circuitry 220 may be configured to monitor a set of externaldata environments (e.g., content delivery networks (CDNs), cloud serviceplatforms, social media platforms, dark websites) and, in someinstances, flag uses of the unencrypted QC detection data or any othersuitable data that made its way into the external data environment.

In some embodiments, the data monitoring circuitry 220 may be configuredto generate alerts and notifications, such as QC detection alert controlsignals, leakage alert control signals, and tampering alert controlsignals. In some embodiments, the data monitoring circuitry 220 may beconfigured to generate a QC detection alert control signal in responseto detection of the electronic information related to the encrypted QCdetection data. For example, the data monitoring circuitry 220 may beconfigured to generate a QC detection alert control signal when thedetected electronic information related to the encrypted QC detectiondata comprises decrypted QC detection data that is the same as the QCdetection data. In some embodiments, the QC detection alert controlsignal may indicate, for example, that the cryptographic technique usedto encrypt the QC detection data has been compromised by quantumcomputing. In some embodiments, the QC detection alert control signalmay be configured to instruct, or cause, the cryptographic circuitry 248to encrypt or re-encrypt data (e.g., enveloped data structures stored inone or more internal or third-party data storage devices) using a PQCtechnique having a cryptostrength that cannot be compromised by thatparticular quantum computer. In some embodiments, the QC detection alertcontrol signal may be configured to instruct, or cause, the UI circuitry258 to generate QC detection alert GUI data (e.g., an electronicnotification, e-mail, pop-up display, audible alarm) and transmit thegenerated QC detection alert GUI data to the input-output circuitry 206,and the input-output circuitry 206 may be configured to receive the QCdetection alert GUI data and display the received QC detection alert GUIdata on one or more display screens.

In some embodiments, the data monitoring circuitry 220 may be configuredto generate a leakage alert control signal in response to detection ofthe electronic information related to the encrypted QC detection data.In some embodiments, the leakage alert control signal may indicate, forexample, that the QC detection data was leaked from an internal dataenvironment, when the QC detection data was leaked from the internaldata environment, who leaked the QC detection data from the internaldata environment (e.g., based on the data lineage of the QC detectiondata), how the QC detection data was leaked from the internal dataenvironment, any other suitable information, or any combination thereof.In some embodiments, the leakage alert control signal may be configuredto instruct, or cause, the communications circuitry 208 to disallow anydata to be transmitted out of the internal data environment associatedwith the leaked QC detection data. In some embodiments, the leakagealert control signal may be configured to instruct, or cause, the UIcircuitry 258 to generate leakage alert GUI data (e.g., an electronicnotification, e-mail, pop-up display, audible alarm) and transmit thegenerated leakage alert GUI data to the input-output circuitry 206, andthe input-output circuitry 206 may be configured to receive the leakagealert GUI data and display the received leakage alert GUI data on one ormore display screens.

In some embodiments, when the detected electronic information related tothe encrypted QC detection data comprises a detected digital signature,the data monitoring circuitry 220 may be configured to verify thedetected digital signature based on the public cryptographic key. Insome embodiments, the data monitoring circuitry 220 may be configured togenerate a tampering alert control signal when the detected electronicinformation related to the encrypted QC detection data further comprisesdetected payload data that has been digitally signed based on thedetected digital signature, the detected digital signature is the sameas the QC detection digital signature, and the detected payload data isdifferent from the QC detection data.

In some embodiments, the tampering alert control signal may indicate,for example, that the QC detection data has been altered but signedusing the same digital signature. For example, the encrypted QCdetection data may comprise QC detection data that has been digitallysigned based on a digital signature (e.g., RSA, such as RSA-PSS; DSA andits elliptic curve variant ECDSA), and the electronic informationrelated to the encrypted QC detection data may comprise payload datathat has been digitally signed based on the digital signature. In someinstances, the payload data may be different from the QC detection data,such as a different fraudulent document digitally signed by the samedigital signature. In some instances, a subset of the payload data maybe the same as a subset of the QC detection data, such as an altereddocument digitally signed by the same digital signature. For example,the QC detection data may comprise a fictitious stock transfer agreementcomprising a first stock transfer attribute indicative of a first amountof transferred shares (e.g., 10 transferred shares), the detectedpayload data may comprise a detected stock transfer agreement comprisinga second stock transfer attribute indicative of a second amount oftransferred shares (e.g., 10,000 transferred shares) different from thefirst amount of transferred shares, and the tampering alert controlsignal may comprise an indication that the fictitious stock transferagreement has been tampered with. In other examples, the detectedpayload data may comprise different buyer or seller information on adigitally signed fictitious electronic mortgage; different ownerinformation on a digitally signed fictitious financial account;different payee or payment amount on a digitally signed fictitiousfinancial transaction (e.g., a fictitious wire transfer, mobile deposit,or electronic check); or any other suitable information.

In some embodiments, the tampering alert control signal may beconfigured to instruct, or cause, the UI circuitry 258 to generatetampering alert GUI data (e.g., an electronic notification, e-mail,pop-up display, audible alarm) and transmit the generated tamperingalert GUI data to the input-output circuitry 206, and the input-outputcircuitry 206 may be configured to receive the tampering alert GUI dataand display the received tampering alert GUI data on one or more displayscreens.

The data access monitoring circuitry 222 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data accessmonitoring circuitry 222 may be configured to monitor the access ofdata, enveloped data structures, any other suitable data or electronicinformation, or any combination thereof. For example, the data accessmonitoring circuitry 222 may be configured to determine that the datahas been accessed, generate a determination that the data has beenaccessed, and transmit the determination that the data has been accessedto any suitable circuitry.

In some embodiments, the data access monitoring circuitry 222 may beconfigured to generate a data access log indicative of a set of dataactivity monitoring information (e.g., database activity monitoringinformation, access credentials, user identification information,machine identification information) associated with electronic access tothe data. For example, the data access monitoring circuitry 222 may beconfigured to generate a data access log comprising a set of timestampsand information indicative of sets of data activity monitoringinformation the data over a period of time (e.g., lifetime of the data;the last three years, or any other suitable period or duration of time),wherein each timestamp in the set of timestamps corresponds to a set ofPQC attributes used to encrypt the data at the time associated with thetimestamp. In another example, the data access monitoring circuitry 222may be configured to generate the set of data activity monitoringinformation and transmit the set of data activity monitoring informationto the processing circuitry 202 and/or the like, which may be configuredto receive the set of data activity monitoring information and generatea data access log based on the set of data activity monitoringinformation.

In some embodiments, the communications circuitry 208 may be configuredto receive the data at a first time, the set of data attributes may be afirst set of data attributes, the data envelope may be a first dataenvelope, the enveloped data structure may be a first enveloped datastructure, and the data access monitoring circuitry 222 may beconfigured to determine that the data has been accessed at a second timelater than the first time. In some embodiments, the data accessmonitoring circuitry 222 may be configured to generate an electronicindication, control signal, metadata, or flag indicating that the datahas been accessed at the second time. In response to the determination(e.g., the electronic indication, control signal, metadata, or flaggenerated by the data access monitoring circuitry 222) that the data hasbeen accessed at the second time, the processing circuitry 202 and/orother circuitry may be configured to generate a second set of dataattributes about the data based on the data and the determination thatthe data has been accessed at the second time, the data envelopegeneration circuitry 216 may be configured to generate a second dataenvelope based on the second set of data attributes, and the datastructure generation circuitry 218 may be configured to generate asecond enveloped data structure based on the second data envelope andthe data. For example, the first set of data attributes may comprise afirst data lineage data attribute indicative of a first data lineage ofthe data, the second set of data attributes may comprise a second datalineage data attribute indicative of a second data lineage of the data,and the first data lineage data attribute may be different from thesecond data lineage data attribute.

The data zone monitoring circuitry 224 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data zonemonitoring circuitry 224 may be configured to monitor the data zoneassociated with data, enveloped data structures, any other suitable dataor electronic information, or any combination thereof. For example, thedata zone monitoring circuitry 224 may be configured to determine thatthe data has transitioned from a first data zone to a second data zone,generate a determination that the data has transitioned from the firstdata zone to the second data zone, and transmit the determination thatthe data has transitioned from the first data zone to the second datazone to any suitable circuitry.

In some embodiments, the communications circuitry 208 may be configuredto receive the data at a first time, the set of data attributes may be afirst set of data attributes comprising a first data zone data attributeindicative of a first data zone associated with the data, the dataenvelope may be a first data envelope, the enveloped data structure maybe a first enveloped data structure, and the data zone monitoringcircuitry 224 may be configured to determine that the data hastransitioned from the first data zone to a second data zone at a secondtime later than the first time. In some embodiments, the data zonemonitoring circuitry 224 may be configured to generate an electronicindication, control signal, metadata, or flag indicating that the datahas transitioned from the first data zone to the second data zone at thesecond time. In response to the determination (e.g., the electronicindication, control signal, metadata, or flag generated by the data zonemonitoring circuitry 224) that the data has transitioned from the firstdata zone to the second data zone at the second time, the processingcircuitry 202 may be configured to generate a second set of dataattributes about the data based on the data and the determination thatthe data has transitioned from the first data zone to the second datazone at the second time. The second set of data attributes may comprisea second data zone data attribute indicative of the second data zoneassociated with the data, and the second data zone data attribute may bedifferent from the first data zone data attribute. The data envelopegeneration circuitry 216 may be configured to generate a second dataenvelope based on the second set of data attributes. The data structuregeneration circuitry 218 may be configured to generate a secondenveloped data structure based on the second data envelope and the data.

In some embodiments, a first enveloped data structure may comprise dataand a first data envelope comprising a set of data attributes. The dataenvelope generation circuitry 216 may be configured to generate a seconddata envelope comprising the set of data attributes and a risk profiledata structure corresponding to the data. The data structure generationcircuitry 218 may be configured to generate a second enveloped datastructure comprising the second data envelope and the data.

The cryptographic circuitry 248 includes hardware components designed orconfigured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the cryptographic circuitry 248 may beconfigured to encrypt data based on a set of PQC attributes, a set ofPQC attributes, or both. In this regard, the cryptographic circuitry 248may include, for example, non-PQC circuitry 250 and PQC circuitry 252.In some embodiments, where the first portion of the electroniccommunication comprises a cryptographic data attribute indicative of asymmetric cryptographic technique and the second portion of theelectronic communication comprises a symmetric cryptographic key, suchas an AES symmetric cryptographic key, the cryptographic circuitry 248may be configured to authenticate a session (e.g., perform acryptographic handshake) with the client device over the non-PQCcommunications channel based on the symmetric cryptographic key that wastransmitted to the client device over the PQC communications channel.

In some embodiments, the cryptographic circuitry 248 may be configuredto authenticate a session (e.g., perform a cryptographic handshake) withthe client device over the non-PQC communications channel based on thequantum cryptographic key that was transmitted to the client device overthe quantum communications channel. In some embodiments, thecryptographic circuitry 248 may be configured to encrypt the secondportion of the electronic communication based on the quantumcryptographic key before transmission to the client device over the PQCcommunications channel.

The non-PQC cryptographic circuitry 250 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the non-PQCcryptographic circuitry 250 may be configured to encrypt the data basedon the set of non-PQC attributes.

The PQC cryptographic circuitry 252 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the PQC circuitry 252may be configured to encrypt the data based on the set of PQC attributesusing a PQC technique.

In some embodiments, the communications circuitry 208 may be configuredto receive the data at a first time, the set of data attributes may be afirst set of data attributes comprising a first cryptographic dataattribute indicative of a first cryptographic technique used to encryptthe data, the data envelope may be a first data envelope, the envelopeddata structure may be a first enveloped data structure, and the PQCcryptographic circuitry 252 may be configured to encrypt the data usinga second cryptographic technique at a second time later than the firsttime. In response to an encryption of the data using the secondcryptographic technique at the second time, the processing circuitry 202may be configured to generate a second set of data attributes about thedata based on the data and the encryption of the data using the secondcryptographic technique at the second time. The second set of dataattributes may comprise a second cryptographic data attribute indicativeof the second cryptographic technique used to encrypt the data at thesecond time, and the second cryptographic data attribute may bedifferent from the first cryptographic data attribute. The data envelopegeneration circuitry 216 may be configured to generate a second dataenvelope based on the second set of data attributes. The data structuregeneration circuitry may be configured to generate a second envelopeddata structure based on the second data envelope and the data. In oneexample, the first cryptographic technique may be a non-PQC technique,and the second cryptographic technique may be a PQC technique. Inanother example, the first cryptographic technique may be a first PQCtechnique, and the second cryptographic technique may be a second PQCtechnique different from the first PQC technique (including, but notlimited to, a different variant of the same PQC cryptographicalgorithm).

In some embodiments, the cryptographic circuitry 248 may be configuredto encrypt data using various recommended cryptographic techniques, suchas non-PQC techniques, PQC techniques, and hybrid PQC techniques (e.g.,hybrid PQC technique={PQC technique, Non-PQC technique}). For example,the recommended cryptographic technique may comprise a hybrid PQCcryptographic mode, such as a signature-based hybrid PQC cryptographicmode consisting of a non-PQC cryptographic signature and a PQCcryptographic signature, where the hybrid PQC cryptographic mode isvalid only if both the non-PQC cryptographic signature and the PQCcryptographic signature are valid (e.g., the PQC system may performvalidation of the non-PQC cryptographic signature according to FIPS140-3; the PQC system may perform validation of the PQC cryptographicsignature using multiple public-key algorithms for X.509 certificates,such as quantum-resistant X.509 Multiple Public Key AlgorithmCertificates).

In some embodiments, the cryptographic circuitry 248 may recommenddifferent cryptographic techniques for encrypting data used by differentlines of business (LOBs) or entities. For example, the cryptographiccircuitry 248 may recommend a first PQC technique for encrypting dataused by a first LOB; a second PQC technique for encrypting data used bya second LOB; a non-PQC technique for encrypting data used by a thirdLOB; and a hybrid PQC technique for encrypting data used by a fourthLOB.

The machine learning circuitry 254 includes hardware components designedor configured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the machine learning circuitry 254 may beconfigured to provide machine learning techniques, any other suitablefunctionality, or any combination thereof. For example, the machinelearning circuitry 254 may be configured to provide a machine learningtechnique, machine learning functionality, or both to the data envelopegeneration circuitry 216, data structure generation circuitry 218, datamonitoring circuitry 220, any other circuitry, or any combinationthereof. In some embodiments, the machine learning circuitry 254 may beconfigured to determine the machine learning technique from among a setof machine learning techniques.

In some embodiments, the machine learning circuitry 254 may beconfigured to provide a machine learning technique, machine learningfunctionality, or both to the processing circuitry 202 for use ingeneration of the set of data attributes about the data. In someembodiments, the machine learning circuitry 254 may be configured toprovide a machine learning technique, machine learning functionality, orboth to the processing circuitry 202 for use in generation of the set ofpolicy attributes about the data.

The data storage circuitry 256 includes hardware components designed orconfigured to request, receive, process, generate, store, and transmitdata, data structures, control signals, and electronic information foruse in PQC. In some embodiments, the data storage circuitry 256 may beconfigured to store data (e.g., unencrypted data, encrypted data,decrypted data, re-encrypted data, double encrypted data, data accesscontrol information, bitstreams of data, links or pointers thereto),data attributes, data envelopes, enveloped data structures, policyinformation, policy attributes, risk profile data structures, non-PQCtechniques, non-PQC performance information, non-PQC attributes, PQCperformance information, PQC techniques, PQC attributes, symmetriccryptographic keys, asymmetric cryptographic keys, any other suitabledata or electronic information, or combinations thereof in a datastorage device, a database management system, any other suitable storagedevice or system, or any combination thereof.

For example, the data storage circuitry 256 may be configured to storean enveloped data structure in a data storage device, a databasemanagement system, or a combination thereof. In some embodiments, thedata storage circuitry 256 may be configured to store the data, datastructures, control signals, and electronic information in the datastorage device, the database management system, or both in real-time andwithout user interactivity.

In some embodiments, the data storage device may comprise, or beimplemented as, memory 204, one or more of the one or more PQC databases106, the one or more database server devices 114 (including, but notlimited to, one or more data storage devices communicatively coupled,either directly or indirectly, to the one or more database serverdevices 114), the one or more remote server devices 116, the one or moreserver devices 110A-110N, the one or more client devices 112A-112N, anyother suitable device or circuitry, or a combination thereof. In someembodiments, the database management system may comprise, or beimplemented as, a database management system (DBMS), such as arelational DMBS (RDBMS) data warehouse, a first non-relational DBMS(e.g., Hadoop distributed file system (HDFS), Hbase), a secondnon-relational DBMS (e.g., content management systems), a datavisualization device, a data mart (e.g., online analytical processing(OLAP) cube), a real-time analytical RDBMS, any other suitable device orcircuitry, or a combination thereof. In some embodiments, the datastorage device, the database management system, or both may comprise, orbe implemented as, one or more decentralized storage devices, such as acloud storage device or system.

The UI circuitry 258 includes hardware components designed or configuredto generate graphical user interface (GUI) data configured to bedisplayed by a display device. For instance, the UI circuitry 258 mayinclude hardware components designed or configured to generate GUI databased on any embodiment or combination of embodiments described withreference to FIGS. 1-6C. In some embodiments, the UI circuitry 258 maybe configured to generate GUI data and transmit the generated GUI datato the input-output circuitry 206, and the input-output circuitry 206may be configured to receive the GUI data and display the received GUIdata on one or more display screens. In some embodiments, the UIcircuitry 258 may include hardware components designed or configured togenerate the GUI data based on one or more portions of the data; dataattributes; data envelopes; enveloped data structures; policyinformation; policy attributes; risk profile data structures; non-PQCtechniques; non-PQC performance information; non-PQC attributes; PQCperformance information; PQC techniques; PQC attributes; symmetriccryptographic keys; asymmetric cryptographic keys; quantum particles;quantum cryptographic keys; quantum one-time pads; any other suitabledata, data structures, electronic information, or quantum information;any links or pointers thereto; and any combinations thereof. The GUIdata may comprise, for example, data attribute GUI data generated basedon the set of data attributes; risk profile GUI data generated based onthe risk profile data structure; PQC optimization GUI data generatedbased on the PQC cryptographic performance information (including, butnot limited to, the set of PQC cryptographic performance attributes),the set of PQC attributes, or both; and data monitoring GUI datagenerated based on the monitoring of enveloped data structures,electronic indications of changes in the monitored enveloped datastructures, any other suitable data, or any combination thereof.

In some embodiments, the UI circuitry 258 may be configured to generatea data attribute GUI based on the set of data attributes. In someembodiments, the UI circuitry 258 may be configured to generate a riskprofile GUI data based on the risk profile data structure. In someembodiments, the UI circuitry 258 may be configured to generate a PQCoptimization GUI based on the PQC performance information (including,but not limited to, the set of PQC performance attributes), the set ofPQC attributes, or both. In some embodiments, the UI circuitry 258 maybe configured to generate a data monitoring GUI based on the monitoringof enveloped data structures, electronic indications of changes in themonitored enveloped data structures, any other suitable data, or anycombination thereof. In some embodiments, the communications circuitry208 may be configured to transmit the data attribute GUI, risk profileGUI, PQC optimization GUI, data monitoring GUI, or a combination thereofto a client device for display by the client device.

It should also be appreciated that, in some embodiments, each of thedata envelope generation circuitry 216, data structure generationcircuitry 218, data monitoring circuitry 220, data access monitoringcircuitry 222, data zone monitoring circuitry 224, cryptographiccircuitry 248, non-PQC cryptographic circuitry 250, PQC cryptographiccircuitry 252, machine learning circuitry 254, data storage circuitry256, and UI circuitry 258 may include a separate processor, speciallyconfigured field programmable gate array (FPGA), ASIC, or cloud utilityto perform the above functions.

In some embodiments, the hardware components described above withreference to data envelope generation circuitry 216, data structuregeneration circuitry 218, data monitoring circuitry 220, data accessmonitoring circuitry 222, data zone monitoring circuitry 224,cryptographic circuitry 248, non-PQC cryptographic circuitry 250, PQCcryptographic circuitry 252, machine learning circuitry 254, datastorage circuitry 256, and UI circuitry 258, may, for instance, utilizePQC callback circuitry 207, communications circuitry 208, or anysuitable wired or wireless communications path to communicate with anode device, a server device (e.g., one or more of server devices110A-110N), a client device (e.g., one or more of client devices112A-112N), a database server device (e.g., one or more of databaseserver devices 114), a remote server device (e.g., one or more of remoteserver devices 116), processing circuitry 202, memory 204, input-outputcircuitry 206, the PQC callback circuitry of another apparatus (e.g.,the PQC callback circuitry 207 of a separate apparatus implementing oneor more portions of apparatus 200 shown in FIG. 2A), the PQC shimcircuitry of another apparatus (e.g., the PQC shim circuitry 260 of aseparate apparatus implementing one or more portions of apparatus 280shown in FIG. 2B), the communications circuitry of another apparatus(e.g., the communications circuitry 208 of a separate apparatusimplementing one or more portions of apparatus 200, 280, or 290), eachother, or any other suitable circuitry or device.

In some embodiments, one or more of the data envelope generationcircuitry 216, data structure generation circuitry 218, data monitoringcircuitry 220, data access monitoring circuitry 222, data zonemonitoring circuitry 224, cryptographic circuitry 248, non-PQCcryptographic circuitry 250, PQC cryptographic circuitry 252, machinelearning circuitry 254, data storage circuitry 256, and UI circuitry 258may be hosted locally by the apparatus 200.

In some embodiments, one or more of the data envelope generationcircuitry 216, data structure generation circuitry 218, data monitoringcircuitry 220, data access monitoring circuitry 222, data zonemonitoring circuitry 224, cryptographic circuitry 248, non-PQCcryptographic circuitry 250, PQC cryptographic circuitry 252, machinelearning circuitry 254, data storage circuitry 256, and UI circuitry 258may be hosted remotely (e.g., by one or more cloud servers) and thusneed not physically reside on the apparatus 200. Thus, some or all ofthe functionality described herein may be provided by a third-partycircuitry. For example, the apparatus 200 may access one or morethird-party circuitries via a networked connection configured totransmit and receive data and electronic information between theapparatus 200 and the third-party circuitries. In turn, the apparatus200 may be in remote communication with one or more of the data envelopegeneration circuitry 216, data structure generation circuitry 218, datamonitoring circuitry 220, data access monitoring circuitry 222, datazone monitoring circuitry 224, cryptographic circuitry 248, non-PQCcryptographic circuitry 250, PQC cryptographic circuitry 252, machinelearning circuitry 254, data storage circuitry 256, and UI circuitry258.

As illustrated in FIG. 2B, an apparatus 280 is shown that represents anexample server device 110, client device 112, database server device114, remote server device 116, any other suitable device, or acombination thereof. The apparatus 280 may include one or more ofprocessing circuitry 202, memory 204, input-output circuitry 206,communications circuitry 208 (including, but not limited to, classicalcommunications circuitry 210 and quantum communications circuitry 212),cryptographic circuitry 248 (including, but not limited to, non-PQCcryptographic circuitry 250, PQC cryptographic circuitry 252, and, insome instances, PQC shim circuitry 260, wherein PQC shim circuitry 260comprises PQC cryptographic circuitry 252), gateway circuitry 264,concentrator circuitry 266, store controller circuitry 268, terminalmanager circuitry 270, POS software upgrade circuitry 272, hardwaresecurity module (HSM) circuitry 274, any other suitable circuitry, orany combination thereof. It will be understood, however, that additionalcomponents providing additional functionality may be included in theapparatus 280 without departing from the scope of the presentdisclosure. The apparatus 280 may be involved in execution of variousoperations described above with respect to FIGS. 1 and 2A and below withrespect to FIGS. 4-6C.

In some embodiments, such as in embodiments where the apparatus 280 is aclassical, non-PQC device that does not include PQC cryptographiccircuitry, the apparatus 280 may be modified to include PQC shimcircuitry 260. The PQC shim circuitry 260 may include hardwarecomponents designed or configured to allow communication with a PQCcallback (e.g., PQC callback circuitry 207 shown in FIG. 2A). The PQCshim circuitry 260 includes hardware components designed or configuredto request, receive, process, generate, and transmit data, datastructures, control signals, and electronic information for use in PQC.For example, PQC shim circuitry 260 may be configured to provide PQCcommunications channel-based cryptographic techniques, such as thetransmission and receipt of sensitive portions (e.g., payloads) ofelectronic communications to a PQC callback over one or more PQCcommunications channels. In some embodiments, the PQC shim circuitry 260may be installed in a network layer of the apparatus 280. In someembodiments, the PQC shim circuitry 260 may comprise the PQCcryptographic circuitry 252.

In some embodiments, the first portion of the electronic communicationmay comprise a PQC request data structure indicative of a request for anacknowledgment or confirmation that the client device (e.g., theapparatus 280) is configured to communicate over a PQC communicationschannel. The client device may be configured to communicate over a PQCcommunications channel if the client device, or a PQC add-on device(e.g., apparatus 290 shown in FIG. 3C) coupled to the client device,comprises the PQC cryptographic circuitry 252, either without the PQCshim circuitry 260 or as a part of the PQC shim circuitry 260. Forexample, the classical communications circuitry 210 may be configured toreceive the first portion of the electronic communication comprising thePQC request data structure from the server device (e.g., the apparatus200 shown in FIG. 2A) over the non-PQC communications channel.

In some embodiments, if the client device is configured to communicateover a PQC communications channel, the classical communicationscircuitry 210 may be configured to transmit, to the server device, a PQCacknowledgement data structure indicating that it is configured tocommunicate over a PQC communications channel. In response to receipt ofthe PQC acknowledgement data structure by the server device, the PQCcallback circuitry 207 of the server device may be configured totransmit the second portion of the electronic communication to theclient device over the PQC communications channel. Subsequently, the PQCcryptographic circuitry 252, either without the PQC shim circuitry 260or as a part of the PQC shim circuitry 260, may be configured to receivethe second portion of the electronic communication from the serverdevice over the PQC communications channel.

In some embodiments, if the client device is not configured tocommunicate over a PQC communications channel, the classicalcommunications circuitry 210 may be configured to transmit, to theserver device, a PQC negative-acknowledgement data structure indicatingthat it is not configured to communicate over a PQC communicationschannel. Alternatively, if the client device is not configured tocommunicate over a PQC communications channel, the classicalcommunications circuitry 210 may be configured to not transmit anyresponse to the server device.

In some embodiments, in response to receipt of the PQCnegative-acknowledgement data structure by the server device, or thelack of receipt of a response by the server device after a predeterminedtime period (e.g., a predetermined period of inactivity or predeterminedelapsed time, such as a timeout), the PQC callback circuitry 207 of theserver device may be configured to transmit a PQC indicator datastructure to the client device over the PQC communications channel. ThePQC indicator data structure may comprise a link to a PQC shimconfigured to allow communication with the PQC callback circuitry 207over the PQC communications channel. Subsequently, the classicalcommunications circuitry 210 may be configured to transmit, to theserver device, a PQC acknowledgement data structure indicating that itis configured to communicate over a PQC communications channel.

In some embodiments, the PQC indicator data structure may furtheridentify the quantum communications channel and indicate that a quantumcryptographic key is to be transmitted over the quantum communicationschannel. The PQC indicator data structure may comprise a link or pointerto the quantum communications channel, a header that identifies thequantum communications channel and comprises other identification androuting information. In some embodiments, the PQC indicator datastructure may comprise a link to the quantum cryptographic key. In someembodiments, the first portion of the electronic communication maycomprise a TLS extension comprising the PQC indicator data structure. Inanother example, the first portion of the electronic communication maycomprise an ISO 8583 extension comprising the PQC indicator datastructure. In another example, the PQC indicator data structure may be,or comprise, or be indicated by, a quantum flag value. In anotherexample, the PQC indicator data structure may comprise a link to aquantum electronic agreement (e.g., a bilateral agreement between thePQC system and the client device to exchange quantum information overthe quantum communications channel) comprising the PQC indicator datastructure.

In some embodiments, the first portion of the electronic communicationmay comprise a quantum request data structure indicative of a requestfor an acknowledgment or confirmation that the client device (e.g., theapparatus 280) is configured to communicate over a quantumcommunications channel. The client device may be configured tocommunicate over a quantum communications channel if the client device,or a PQC add-on device (e.g., apparatus 290 shown in FIG. 3C) coupled tothe client device, comprises the quantum communications circuitry 212.For example, the classical communications circuitry 210 may beconfigured to receive the first portion of the electronic communicationcomprising the quantum request data structure from the server device(e.g., the apparatus 200 shown in FIG. 2A) over the non-PQCcommunications channel.

In some embodiments, if the client device is configured to communicateover a quantum communications channel, the classical communicationscircuitry 210 may be configured to transmit, to the server device, aquantum acknowledgement data structure indicating that it is configuredto communicate over a quantum communications channel. In response toreceipt of the quantum acknowledgement data structure by the serverdevice, the quantum communications circuitry 212 of the server devicemay be configured to transmit the quantum cryptographic key to theclient device over the quantum communications channel. The quantumcommunications circuitry 212 may be configured to receive the quantumcryptographic key from the server device over the quantum communicationschannel. Subsequently, the cryptographic circuitry 248 may be configuredto authenticate a session (e.g., perform a cryptographic handshake) withthe client device over the non-PQC communications channel based on thequantum cryptographic key that was transmitted to the client device overthe quantum communications channel.

In some embodiments, if the client device is not configured tocommunicate over a quantum communications channel, the classicalcommunications circuitry 210 may be configured to transmit, to theserver device, a quantum negative-acknowledgement data structureindicating that the client device is not configured to communicate overa quantum communications channel. Alternatively, if the client device isnot configured to communicate over a quantum communications channel, theclassical communications circuitry 210 may be configured to not transmitany response to the server device. In some embodiments, in response toreceipt of the quantum negative-acknowledgement data structure by theserver device, or the lack of receipt of a response by the server deviceafter a predetermined time period (e.g., a predetermined period ofinactivity or predetermined elapsed time, such as a timeout), thequantum communications circuitry 212 of the server device may beconfigured to not transmit the quantum cryptographic key or the secondportion of the electronic communication to the client device.

The gateway circuitry 264 includes hardware components designed orconfigured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the gateway circuitry 264 may be configured toprovide transactions management, payment processing, any other suitablefunctionality, and any combination thereof for one or more POS or otherdevices communicatively coupled to the apparatus 280.

The concentrator circuitry 266 includes hardware components designed orconfigured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the concentrator circuitry 266 may beconfigured to connect multiple POS or other devices to the apparatus280. For example, the concentrator circuitry 266 may be configured toprovide communications management, connectivity, any other suitablefunctionality, and any combination thereof for one or more POS or otherdevices communicatively coupled to the apparatus 280.

The store controller circuitry 268 includes hardware components designedor configured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the store controller circuitry 268 may beconfigured to provide applications, services, any other suitablefunctionality, and any combination thereof for one or more POS or otherdevices communicatively coupled to the apparatus 280.

The terminal manager circuitry 270 includes hardware components designedor configured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the terminal manager circuitry 270 may beconfigured to provide terminal management, terminal monitoring, terminalcontrol, terminal updating, any other suitable functionality, and anycombination thereof for one or more POS or other devices communicativelycoupled to the apparatus 280.

The POS software upgrade circuitry 272 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the POS softwareupgrade circuitry 272 may be configured to provide software upgradingfunctionality, proxy upgrade functionality (e.g., upgrade to a PQC orPQC-related proxy), any other suitable functionality, and anycombination thereof for one or more POS or other devices communicativelycoupled to the apparatus 280. In some embodiments, the POS softwareupgrade circuitry 272 may be configured to upgrade the POS proxy ofconnected POS.

The HSM circuitry 274 includes hardened, tamper-resistant hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, the HSMcircuitry 274 may be configured to provide: protection for cryptographickeys, customer personal identification numbers (PINs), magnetic stripedata, EMV (originally Europay, Mastercard, and Visa) chip data, andmobile application counterparts thereof (e.g., virtual debit cards andcredit cards stored in a user's mobile wallet); native cryptographicsupport for card scheme payment applications; any other suitablefunctionality; and any combination thereof for one or more POS or otherdevices communicatively coupled to the apparatus 280. In someembodiments, the HSM circuitry 274 may be configured to provide:personal identification number (PIN) generation, management andvalidation; PIN block translation during the network switching of ATMand POS transactions; card, user, and cryptogram validation duringpayment transaction processing; payment credential issuing for paymentcards and mobile applications; point-to-point encryption (P2PE) keymanagement and secure data decryption; secure key sharing with thirdparties to facilitate secure communications; any other suitablefunctionality; and any combination thereof.

It should also be appreciated that, in some embodiments, each of thecryptographic circuitry 248, non-PQC cryptographic circuitry 250, PQCcryptographic circuitry 252, PQC shim circuitry 260, gateway circuitry264, concentrator circuitry 266, store controller circuitry 268,terminal manager circuitry 270, POS software upgrade circuitry 272, andHSM circuitry 274 may include a separate processor, specially configuredFPGA, ASIC, or cloud utility to perform the above functions.

In some embodiments, the hardware components described above withreference to cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, PQC cryptographic circuitry 252, PQC shim circuitry 260,gateway circuitry 264, concentrator circuitry 266, store controllercircuitry 268, terminal manager circuitry 270, POS software upgradecircuitry 272, and HSM circuitry 274, may, for instance, utilizecommunications circuitry 208 or any suitable wired or wirelesscommunications path to communicate with a node device, a server device(e.g., one or more of server devices 110A-110N), a client device (e.g.,one or more of client devices 112A-112N), a database server device(e.g., one or more of database server devices 114), a remote serverdevice (e.g., one or more of remote server devices 116), processingcircuitry 202, memory 204, input-output circuitry 206, the PQC callbackcircuitry of another apparatus (e.g., the PQC callback circuitry 207 ofa separate apparatus implementing one or more portions of apparatus 200shown in FIG. 2A), the PQC shim circuitry of another apparatus (e.g.,the PQC shim circuitry 260 of a separate apparatus implementing one ormore portions of apparatus 280), the communications circuitry of anotherapparatus (e.g., the communications circuitry 208 of a separateapparatus implementing one or more portions of apparatus 200, 280, or290), each other, or any other suitable circuitry or device.

In some embodiments, one or more of the cryptographic circuitry 248,non-PQC cryptographic circuitry 250, PQC cryptographic circuitry 252,PQC shim circuitry 260, gateway circuitry 264, concentrator circuitry266, store controller circuitry 268, terminal manager circuitry 270, POSsoftware upgrade circuitry 272, and HSM circuitry 274 may be hostedlocally by the apparatus 280.

In some embodiments, one or more of the cryptographic circuitry 248,non-PQC cryptographic circuitry 250, PQC cryptographic circuitry 252,PQC shim circuitry 260, gateway circuitry 264, concentrator circuitry266, store controller circuitry 268, terminal manager circuitry 270, POSsoftware upgrade circuitry 272, and HSM circuitry 274 may be hostedremotely (e.g., by one or more cloud servers) and thus need notphysically reside on the apparatus 280. Thus, some or all of thefunctionality described herein may be provided by a third-partycircuitry. For example, the apparatus 280 may access one or morethird-party circuitries via a networked connection configured totransmit and receive data and electronic information between theapparatus 280 and the third-party circuitries. In turn, the apparatus280 may be in remote communication with one or more of the cryptographiccircuitry 248, non-PQC cryptographic circuitry 250, PQC cryptographiccircuitry 252, PQC shim circuitry 260, gateway circuitry 264,concentrator circuitry 266, store controller circuitry 268, terminalmanager circuitry 270, POS software upgrade circuitry 272, and HSMcircuitry 274.

As illustrated in FIG. 2C, an apparatus 290 is shown that represents anexample PQC add-on device configured to be communicatively coupled(e.g., wirelessly connected, electrically connected) to a client device,such as a server device 110, client device 112, database server device114, remote server device 116, any other suitable device, or acombination thereof. In some embodiments, the apparatus 290 may be a PQCperipheral device communicatively coupled to the client device. In someembodiments, the apparatus 290 may be, or comprise, a PQC ASIC installedwithin a housing of the client device.

In some embodiments, the apparatus 290 may include one or more ofprocessing circuitry 202, memory 204, input-output circuitry 206,communications circuitry 208 (including, but not limited to, classicalcommunications circuitry 210 and quantum communications circuitry 212),cryptographic circuitry 248 (including, but not limited to, non-PQCcryptographic circuitry 250 and PQC cryptographic circuitry 252), anyother suitable circuitry, or any combination thereof. It will beunderstood, however, that additional components providing additionalfunctionality may be included in the apparatus 290 without departingfrom the scope of the present disclosure. The apparatus 290 may beinvolved in execution of various operations described above with respectto FIGS. 1 and 2A and below with respect to FIGS. 4-6C.

In some embodiments, the apparatus 290 may hardware components designedor configured to allow communication with a PQC callback (e.g., PQCcallback circuitry 207 shown in FIG. 2A). The apparatus 290 includeshardware components designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. For example, the apparatus 290may be configured to provide PQC communications channel-basedcryptographic techniques, such as the transmission and receipt ofsensitive portions (e.g., payloads) of electronic communications to aPQC callback over one or more PQC communications channels.

It should also be appreciated that, in some embodiments, each of thecryptographic circuitry 248, non-PQC cryptographic circuitry 250, PQCcryptographic circuitry 252 may include a separate processor, speciallyconfigured FPGA, ASIC, or cloud utility to perform the above functions.

In some embodiments, the hardware components described above withreference to cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, and PQC cryptographic circuitry 252, may, for instance,utilize communications circuitry 208 or any suitable wired or wirelesscommunications path to communicate with a node device, a server device(e.g., one or more of server devices 110A-110N), a client device (e.g.,one or more of client devices 112A-112N), a database server device(e.g., one or more of database server devices 114), a remote serverdevice (e.g., one or more of remote server devices 116), processingcircuitry 202, memory 204, input-output circuitry 206, the PQC callbackcircuitry of another apparatus (e.g., the PQC callback circuitry 207 ofa separate apparatus implementing one or more portions of apparatus 200shown in FIG. 2A), the PQC shim circuitry of another apparatus (e.g.,the PQC shim circuitry 260 of a separate apparatus implementing one ormore portions of apparatus 280 shown in FIG. 2B), the communicationscircuitry of another apparatus (e.g., the communications circuitry 208of a separate apparatus implementing one or more portions of apparatus200, 280, or 290), each other, or any other suitable circuitry ordevice.

In some embodiments, one or more of the cryptographic circuitry 248,non-PQC cryptographic circuitry 250, PQC cryptographic circuitry 252 maybe hosted locally by the apparatus 290.

In some embodiments, one or more of the cryptographic circuitry 248,non-PQC cryptographic circuitry 250, PQC cryptographic circuitry 252 maybe hosted remotely (e.g., by one or more cloud servers) and thus neednot physically reside on the apparatus 290. Thus, some or all of thefunctionality described herein may be provided by a third-partycircuitry. For example, the apparatus 290 may access one or morethird-party circuitries via a networked connection configured totransmit and receive data and electronic information between theapparatus 290 and the third-party circuitries. In turn, the apparatus290 may be in remote communication with one or more of the cryptographiccircuitry 248, non-PQC cryptographic circuitry 250, PQC cryptographiccircuitry 252.

Although some of these components of apparatuses 200, 280, and 290 aredescribed with respect to their functional capabilities, it should beunderstood that the particular implementations necessarily include theuse of particular hardware to implement such functional capabilities. Itshould also be understood that certain of these components may includesimilar or common hardware. For example, two sets of circuitries mayboth leverage use of the same processor, network interface, quantumcommunications interface, optoelectronic components, storage medium,machine learning circuitry, or the like to perform their associatedfunctions, such that duplicate hardware is not required for each set ofcircuitries. It should also be appreciated that, in some embodiments,one or more of these components may include a separate processor,specially configured FPGA, ASIC, or cloud utility to perform itscorresponding functions as described herein.

The use of the term “circuitry” as used herein with respect tocomponents of apparatuses 200, 280, and 290 includes particular hardwareconfigured to perform the functions associated with respective circuitrydescribed herein. While the term “circuitry” should be understoodbroadly to include hardware, in some embodiments, circuitry may alsoinclude software for configuring the hardware. For example, in someembodiments, “circuitry” may include processing circuitry, storagemedia, network interfaces, quantum interfaces, input-output devices,optoelectronic components, and other components. In some embodiments,other elements of apparatuses 200, 280, and 290 may provide orsupplement the functionality of particular circuitry. For example, theprocessing circuitry 202 may provide processing functionality, memory204 may provide storage functionality, classical communicationscircuitry 210 may provide network interface functionality, and quantumcommunications circuitry 212 may provide quantum interface functionalityamong other features.

In some embodiments, various components of one or more of theapparatuses 200, 280, or 290 may be hosted remotely (e.g., by one ormore cloud servers) and thus need not physically reside on thecorresponding apparatus 200, 280, or 290. Thus, some or all of thefunctionality described herein may be provided by third-party circuitry.For example, a given apparatus 200, 280, or 290 may access one or morethird-party circuitries via any sort of networked connection thatfacilitates transmission of data and electronic information between theapparatus 200, 280, or 290 and the third-party circuitries. In turn,that apparatus 200, 280, or 290 may be in remote communication with oneor more of the other components described above as being comprised bythe apparatus 200, 280, or 290.

As will be appreciated, computer program instructions and/or other typeof code may be loaded onto a computer, processor or other programmableapparatus's circuitry to produce a machine, such that the computer,processor, or other programmable circuitry that executes the code on themachine creates the means for implementing various functions describedherein.

As described above and as will be appreciated based on this disclosure,embodiments of the present disclosure may be configured as systems,apparatuses, methods, optoelectronic devices, mobile devices, backendnetwork devices, computer program products, other suitable devices, andcombinations thereof. Accordingly, embodiments may comprise variousmeans including entirely of hardware or any combination of software withhardware. Furthermore, embodiments may take the form of a computerprogram product on at least one non-transitory computer-readable storagemedium having computer-readable program instructions (e.g., computersoftware) embodied in the storage medium. Any suitable computer-readablestorage medium may be utilized including non-transitory hard disks,CD-ROMs, flash memory, optical storage devices, or magnetic storagedevices. As will be appreciated, any computer-executable program codeinstructions, any other type of code described herein, and anycombination thereof may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor, or other programmable circuitry that executes thecode on the machine creates the means for implementing variousfunctions, including the functions described herein.

The one or more server devices 110A-110N, one or more client devices112A-112N, one or more database server devices 114, and one or moreremote server devices 116 described with reference to FIG. 1 may beembodied by one or more computing devices, servers, data storagedevices, or systems that also may include processing circuitry, memory,input-output circuitry, and communications circuitry. For example, aserver device 110 may be a database server on which computer code (e.g.,C, C++, C#, java, a structured query language (SQL), a data querylanguage (DQL), a data definition language (DDL), a data controllanguage (DCL), a data manipulation language (DML)) is running orotherwise being executed by processing circuitry. In another example, aclient device 112 may be a smartphone on which an app (e.g., a mobiledatabase app) is running or otherwise being executed by processingcircuitry. As it relates to operations described in the presentdisclosure, the functioning of these devices may utilize componentssimilar to the similarly named components described above with referenceto FIG. 2. Additional description of the mechanics of these componentsis omitted for the sake of brevity. These device elements, operatingtogether, provide the respective computing systems with thefunctionality necessary to facilitate the communication of data with thePQC system described herein.

FIGS. 3A, 3B, 3C, 3D, and 3E illustrate example PQC system architecturesconfigured to perform various operations in accordance with some exampleembodiments described herein.

FIG. 3A illustrates an example PQC system architecture 300 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 300 may comprise,for example, PQC system 302 and client device 320.

In some embodiments, the PQC system 302 may comprise, for example, oneor more data storage devices 306 comprising search and other functions,one or more PQC server devices 304, one or more non-PQC techniquestorage devices 308 storing non-PQC techniques and non-PQC cryptographicperformance information related thereto, one or more PQC callbacks 310,one or more PQC technique storage devices 312 storing PQC techniques andPQC cryptographic performance information related thereto, and data 314.In some embodiments, the PQC system 302 may be configured to perform PQCin accordance with some example embodiments described herein (e.g., asdescribed with reference to apparatus 200 shown in FIG. 2A).

In some embodiments, the client device 320 may comprise communicationscircuitry configured to communicate with the one or more PQC serverdevices 304 over one or more non-PQC communications channels 324. Theclient device 320 may comprise, for example, a PQC shim 322 configuredto communicate with the one or more PQC callbacks 310 over one or morePQC communications channels 326. In some embodiments, the client device320 may be configured to perform PQC in accordance with some exampleembodiments described herein (e.g., as described with reference toapparatus 280 shown in FIG. 2B, wherein apparatus 280 comprises the PQCshim circuitry 260, and the PQC shim circuitry 260 comprises the PQCcryptographic circuitry 252).

FIG. 3B illustrates an example PQC system architecture 392 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 392 may comprise,for example, the PQC system 302, a client device 330, and one or morePOS 338A-338N.

In some embodiments, the client device 330 may comprise the PQC shim332, an HSM 336, and a POS interface device 334 comprising aconcentrator, gateway, store controller, terminal manager, and upgradedPOS proxy. The POS interface device 334 may be configured to communicatewith the POS devices 338A-338N over one or more non-PQC communicationschannels. The POS interface device 334 may be further configured tocommunicate with the one or more PQC server devices 304 over one or morenon-PQC communications channels 324. The PQC shim 322 configured tocommunicate with the one or more PQC callbacks 310 over one or more PQCcommunications channels 326. In some embodiments, the client device 330may be configured to perform PQC in accordance with some exampleembodiments described herein (e.g., as described with reference toapparatus 280 shown in FIG. 2B, wherein apparatus 280 comprises the PQCshim circuitry 260, and the PQC shim circuitry 260 comprises the PQCcryptographic circuitry 252).

FIG. 3C illustrates an example PQC system architecture 394 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 394 may comprise,for example, the PQC system 302, a client device 340, and a PQC add-ondevice 342.

The client device 340 may comprise communications circuitry configuredto communicate with the one or more PQC server devices 304 over one ormore non-PQC communications channels 324. The PQC add-on device 342 maybe communicatively coupled to the client device 340 and configured tocommunicate with the one or more PQC callbacks 310 over one or more PQCcommunications channels 326. In some embodiments, the client device 340may not be configured to perform PQC in accordance with some exampleembodiments described herein (e.g., as described with reference toapparatus 280 shown in FIG. 2B, wherein apparatus 280 includes neitherthe PQC cryptographic circuitry 252 nor the PQC shim circuitry 260). Insome embodiments, the PQC add-on device 342 may be configured to performPQC for the client device 340 (e.g., on behalf of the client device 340)in accordance with some example embodiments described herein (e.g., asdescribed with reference to apparatus 290 shown in FIG. 2C).

FIG. 3D illustrates an example PQC system architecture 396 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 396 may comprise,for example, the PQC system 302, a client device 350, a PQC add-ondevice 352, and one or more POS 338A-338N.

In some embodiments, the client device 350 may comprise an HSM 356 and aPOS interface device 354 comprising a concentrator, gateway, storecontroller, terminal manager, and upgraded POS proxy. The POS interfacedevice 354 may be configured to communicate with the POS 338A-338N overone or more non-PQC communications channels. The POS interface device354 may be further configured to communicate with the one or more PQCserver devices 304 over one or more non-PQC communications channels 324.The PQC add-on device 352 may be communicatively coupled to the clientdevice 350 and configured to communicate with the one or more PQCcallbacks 310 over one or more PQC communications channels 326. In someembodiments, the client device 350 may not be configured to perform PQCin accordance with some example embodiments described herein (e.g., asdescribed with reference to apparatus 280 shown in FIG. 2B, whereinapparatus 280 includes neither the PQC cryptographic circuitry 252 northe PQC shim circuitry 260). In some embodiments, the PQC add-on device352 may be configured to perform PQC for the client device 350 (e.g., onbehalf of the client device 350) in accordance with some exampleembodiments described herein (e.g., as described with reference toapparatus 290 shown in FIG. 2C).

FIG. 3E illustrates an example PQC system architecture 398 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 398 may comprise,for example, the PQC system 302 and a set of client devices comprising aclient device 360A and a second client device 360B. Further to theembodiments shown in FIGS. 3A-3D, the PQC system 302 may furthercomprise quantum communications circuitry 316 and one or more quantumcryptographic technique storage devices 318 storing quantumcryptographic techniques and quantum cryptographic performanceinformation related thereto.

In some embodiments, the first client device 360A and the second clientdevice 360B may be embodied by any of the client devices shown in FIGS.3A-3D, such as client device 320; client device 330; client device 340and PQC add-on device 342; or client device 350 and PQC add-on device352. Further still to the embodiments shown in FIGS. 3A-3D, the firstclient device 360A may comprise quantum communications circuitry 362A,and the second client device 360B may comprise quantum communicationscircuitry 362B. In some embodiments, the first client device 360A may becommunicatively coupled to a PQC add-on device comprising the quantumcommunications circuitry 362A, and the second client device 360B may becommunicatively coupled to a PQC add-on device comprising the quantumcommunications circuitry 362B.

In some embodiments, the client device 360A and the client device 360Bmay comprise communications circuitry configured to communicate with theone or more PQC server devices 304 over one or more non-PQCcommunications channels 324A and 324B, respectively, and to communicatewith each other over one or more non-PQC communications channels 374. Insome embodiments, the client device 360A and the client device 360B maycomprise communications circuitry configured to communicate with the oneor more PQC callbacks 310 over one or more PQC communications channels326A and 326B, respectively, and to communicate with each other over oneor more PQC communications channels 376. In some embodiments, the clientdevice 360A and the client device 360B may comprise quantumcommunications circuitry 362A and 362B, respectively, configured tocommunicate with the quantum communications circuitry 316 over one ormore quantum communications channels 328A and 228B, respectively, and tocommunicate with each other over one or more quantum communicationschannels 378.

Example Operations for PQC

Various embodiments provide methods, systems, apparatuses, computerprogram products, and/or the like for securely storing possiblysensitive information/data via an external data repository 120. Invarious embodiments, an external data repository 120 is operated byand/or on behalf of an entity other than the data owner. In variousembodiments, an external data repository 120 comprises computer readablememory (e.g., volatile and/or non-volatile memory) that may be coupledto processing circuitry, communications circuitry, and/or the like. Forexample, the PQC system 102, PQC server devices 104, PQC databases 106,server devices 110A-110N, client devices 112A-112N, database serverdevices 114, and/or remote server devices 116 may be operated by a firstentity that is the owner of various data/information instances. Thefirst entity may store various data/information instances in theexternal data repository 120, which is operated by and/or on behalf of athird entity. In an example embodiment, the external data repository 120may be used to store and/or access various information/data instances bythe first entity. In various embodiments, the external data repository120 may be used to disseminate various information/data instances to oneor more second entities that are authorized to access the variousinformation/data instances.

For example, in various embodiments, a PQC system 102, PQC server device104, PQC database 106, server device 110A-110N, client device 112A-112N,database server device 114, remote server device 116 and/or apparatus200 may generate one or more blockchains and corresponding side chains.In various embodiments, the PQC system 102, PQC server device 104, PQCdatabase 106, server device 110A-110N, client device 112A-112N, databaseserver device 114, remote server device 116 and/or apparatus 200 mayprovide the one or more blockchains and corresponding side chains forstorage by an external data repository 120. In various embodiments, thePQC system 102, PQC server device 104, PQC database 106, server device110A-110N, client device 112A-112N, database server device 114, remoteserver device 116 and/or apparatus 200 may provide information/datainstances to be written to one or more blockchains and correspondingside chains and stored by an external data repository 120. In variousembodiments, the PQC system 102, PQC server device 104, PQC database106, server device 110A-110N, client device 112A-112N, database serverdevice 114, remote server device 116 and/or apparatus 200 may access oneor more blocks from a blockchain and/or first and/or second side chainblocks from corresponding side chains from external data repository 120.

In various embodiments, a stream of information/data may be written to ablockchain. For example, the stream of information/data may includeinformation/data instances corresponding to transactions, events, and/orthe like. In an example embodiment, the stream of information/data iswritten to the blockchain by a first entity/party computing entity(e.g., a PQC system 102, PQC server device 104, PQC database 106, serverdevice 110, client device 112, database server device 114, remote serverdevice 116, apparatus 200, 280, 290, PQC system 302, and/or clientdevice 320, 330, 340, 350, 360) which is operated by theinformation/data owner. In an example embodiment, the first entity/partycomputing entity may generate blocks for the blockchain and theblockchain may be stored (and/or at least a copy of the blockchain) maybe stored by an external data repository 120. In various embodiments,two or more side chains may be generated and/or stored by the firstentity/party computing entity and/or the external data repository 120.

FIG. 4 illustrates an example blockchain and side chain architecture400, in accordance with an example embodiment. In an example embodiment,a blockchain and side chain architecture 400 comprises a primaryblockchain 402 and at least two side chains (e.g., first side chain 412and second side chain 422). In an example embodiment, the primaryblockchain 402 is stored by a computing entity operated by the firstentity/party (e.g., the data owner of the information/data in the streamof information/data) and the first and/or second side chains 412, 422are stored in the external data repository 120.

As should be understood, each of the primary blockchain 402, first sidechain 412, and second side chain 422 comprise a root block (e.g., Block0, Block C0, Block P0). The primary blockchain 402 further comprises aplurality of blocks 404 storing instances of information/data from thestream of information/data. FIG. 6A illustrates an example block datastructure 610 that may be used for blocks 404, in an example embodiment.For example, the block data structure 610 comprises a header 612,content 614 comprising one or more records each corresponding to aninformation/data instance from the stream of information/data, and alink 618 that links the block 404 to the immediately previous block inthe primary blockchain 402. For example, the link 618 may be a hashvalue for the immediately previous block 404 in the primary blockchain402. In various embodiments, the header 612 may comprise metadatacorresponding to blockchain 402, the block 404, and/or the contentthereof.

The first side chain 412 comprises one or more first side chain blocks414. In various embodiments, each first side chain block 414 correspondsto a first set 416 (e.g., 416A, 416B) of blocks 404. Each of the firstsets 416 of block 404 comprises X blocks, where X is an integer greaterthan or equal to one. In various embodiments, the first sets 416 arenon-overlapping sets and comprise consecutive blocks. For example, afirst set 416A corresponding to first side chain block 414 Block C1comprises blocks 404 Block 1 and Block 2 (and optionally Block 0).However, as the first set 416A does not include Block 3, the first set416A will not include Block 4. Moreover, first set 416B corresponding tofirst side chain block 414 Block C2 comprises blocks 404 Block 3 andBlock 4. Thus, the first sets 416A and 416B are non-overlapping, meaningthat the first sets 416A and 416B do not have any component blocks 404in common.

In various embodiments, the content of a first side chain block 414 maycomprise content and/or a verification of the content of one or moreblocks of the first set 416 of blocks 404 that correspond to the firstside chain block 414. For example, a first side chain block 414 maycomprise a verification of the content of one or more blocks 404 of thefirst set 416 corresponding to the first side chain block 414, encryptedinformation/data instances from the one or more blocks 404 of the set416 corresponding to the first side chain block 414, and/or the like.For example, FIG. 6B illustrates an example first side chain block datastructure 620 that may be used for blocks 414, in an example embodiment.For example, the first side chain block data structure 620 comprises aheader 622, content 624 comprising encrypted versions of one or morerecords from one or more block 404 of the first set 416 corresponding tothe first side chain block 414 ad/or an indication of which blocks 404of the first set 416 corresponding to the first side chain block 414were verified, a signature 626, and a link 628 that links the block 414to the immediately previous first side chain block 614 in the first sidechain 412. For example, the link 628 may be a hash value for theimmediately previous first side chain block 414 in the first side chain412. In various embodiments, the header 622 may comprise metadatacorresponding to the first side chain 412, the first side chain block414, and/or the content thereof. In an example embodiment, the content624 of a first side chain block 414 comprises a hash of one or moreblocks 404 in the first set 416 corresponding to the first side chainblock 414 or a hash of one or more records of one or more blocks 404 inthe first set 416 corresponding to the first side chain block 414. In anexample embodiment, the signature 626 is a cryptographic signatureapplied to the first side chain block 614. For example, the first sidechain block 614 may be signed using a first digital signature algorithm.In an example embodiment, the signature 626 and/or any cryptographictechnique used to encrypt the content 624 of the first side chain block614 is a classical and/or non-PQC technique. For example, the firstdigital signature algorithm may be a classical and/or non-PQC digitalsignature algorithm.

The second side chain 422 comprises one or more second side chain blocks424. In various embodiments, each second side chain block 424corresponds to a second set 426 (e.g., 426A) of first side chain blocks414 and/or blocks 404. Each of the second sets 426 of first side chainblocks 414 and/or blocks 404 corresponds to Y blocks 404 of the primaryblockchain 402. In various embodiments, Y is an integer that is greaterthan or equal to X. In various embodiments, the second sets 426 arenon-overlapping sets and comprise consecutive blocks 404 and/or firstside chain blocks 414. For example, a second set 426A corresponding tosecond side chain block 424 Block P1 comprises blocks 404 Blocks 1-4 andfirst side chain blocks 414 Blocks C1 and C2 (and optionally Block 0and/or Block C0). However, as the second set 426A does not include Block5 or Block C3, the second set 426A will not include Block 6 or Block C4.Moreover, second set 416B corresponding to second side chain block 424Block P2 comprises blocks 404 Blocks 5-8 and/or first side chain blocks414 Blocks C3 and C4. Thus, the second sets 426A and 426B arenon-overlapping, meaning that the second sets 426A and 426B do not haveany component blocks 404 and/or component first side chain blocks 414 incommon. However, each second set 426 will overlap at least in part withat least one first set 416.

In various embodiments, the content of a second side chain block 424 maycomprise content and/or a verification of the content of one or moreblocks 404 and/or first side chain blocks 414 of the set 426 of blocks404 and/or first side chain blocks 414 that correspond to the secondside chain block 424. For example, a second side chain block 424 may becomprise a verification of the content of one or more blocks 404 and/orfirst side chain blocks 414 of the second set 426 corresponding to thesecond side chain block 424, encrypted information/data instances fromthe one or more blocks 404 and/or first side chain blocks 414 of thesecond set 426 corresponding to the second side chain block 424, and/orthe like.

For example, FIG. 8C illustrates an example second side chain block datastructure 630 that may be used for second side chain blocks 424, in anexample embodiment. For example, the second side chain block datastructure 630 comprises a header 632, content 634 comprising encryptedversions of one or more records from one or more block 404 and/or firstside chain blocks 414 of the second set 426 corresponding to the secondside chain block 424 ad/or an indication of which blocks 404 and/orfirst side chain blocks 414 of the second set 426 corresponding to thesecond side chain block 424 were verified, a signature 636, and a link638 that links the block 424 to the immediately previous block in thesecond side chain 422. For example, the link 628 may be a hash value forthe immediately previous second side chain block 424 in the second sidechain 422. In various embodiments, the header 632 may comprise metadatacorresponding to the second side chain 422, the second side chain block424, and/or the content thereof. In an example embodiment, the content634 of a second side chain block 424 comprises a hash of one or moreblocks 404 and/or a hash of one or more first side chain blocks 414 inthe second set 426 corresponding to the second side chain block 414 or ahash of one or more records of one or more blocks 404 and/or first sidechain blocks 414 in the second set 426 corresponding to the second sidechain block 424.

In an example embodiment, the signature 636 is a cryptographic signatureapplied to the second side chain block 624. For example, the second sidechain block 624 may be signed using a second digital signaturealgorithm. In an example embodiment, the signature 636 and/or anycryptographic technique used to encrypt the content 634 of the secondside chain block 624 is a PQC technique. In an example embodiment, thesignature 636 and/or the PQC technique may be determined based on thestates of one or more quantum particles that are confined, for example,by PQC cryptographic circuitry 252. In an example embodiment, thesignature 636 and/or any cryptographic technique used to encrypt thecontent 634 of the second side chain block 624 is a PQC technique. Forexample, the second digital signature algorithm may be a PQC digitalsignature algorithm. In various embodiments, the number of blocks 404 ofthe primary blockchain 402 in a first set 416 is greater than the numberof blocks 404 of the primary blockchain 402 in a second set 426 toaccount for the longer amount of time required to perform PQC techniquesand/or to apply PQC signatures to side chain blocks.

In various embodiments, the blocks 404 of the primary blockchain 402 maynot be encrypted and/or may be encrypted and/or signed using classicaland/or non-PQC techniques. In various embodiments, the first side chainblocks 414 of the first side chain 412 may comprise content encryptedand/or be signed using classical and/or non-PQC techniques. In variousembodiments, the second side chain blocks 424 of the second side chain422 may comprise content encrypted and/or be signed using PQCtechniques. Thus, the first and second side chains 412, 422 provide amigration path from classical/non-PQC encryption and/or verification(e.g., signing) of information/data instances stored in the records of aprimary blockchain 402 (e.g., via the first side chain 412) to PQCencryption and/or verification (e.g., signing) of information/datainstances stored in the records of the primary block chain 402 and/orfirst side chain 412 (e.g., via the second side chain 422).

FIG. 7 provides a flowchart illustrating processes, procedures, and/oroperations of a method 500 that may be performed (e.g., by a firstentity/party computing entity) to generate and store a first and secondside chains 412, 422 corresponding to a primary blockchain 402. Invarious embodiments, the first and/or second side chains 412, 422 arestored by an external data repository 120. Starting at step/operation502, the first entity/party computing entity may write recordscomprising information/data instances to the primary blockchain 402(e.g., via processing circuitry 202, memory 204, communication circuitry208, and/or the like). For example, the first entity/party computingentity may receive, monitor, generate, and/or the like a stream ofinformation/data. Information/data instances may be extracted from thestream of information/data and written to blocks 404 that may then bewritten to the primary blockchain 402. In an example embodiment, theblocks first entity/party computing entity may use a digital signaturealgorithm (e.g., a non-PQC digital signature algorithm) to digitallysign one or more blocks 404 of the primary blockchain 402.

At step/operation 504, the first entity/party computing entity may writea first side chain block 414 corresponding to a first set 416 of blocks404 of the primary blockchain 402 (e.g., via processing circuitry 202,memory 204, communication circuitry 208, and/or the like). For example,the first entity/party computing entity may determine that a new firstset 416 of blocks 404 has been added to the primary block chain 402.This new first set 416 of blocks 404 may be used to generate a new firstside chain block 414. For example, it may be determined that X blocks404 have been written to the primary block chain 402 since a first sidechain block 414 was written to the first side chain 412 and/or since thelast block 404 of the immediately previous first set 416 of blocks 404was written to the primary blockchain 402. In an example embodiment,this determination may trigger a first check to be performed. In anexample embodiment, the first check may include generating a hash of oneor more blocks 404 of the first set 416 corresponding to the new firstside chain block 414 and comparing that hash to a hash (e.g., link 618)contained in an immediately succeeding block 404. If the hashes match,the first check may determine that the one or more block 404 areverified. In an example embodiment, the one or more blocks 404 of thefirst set 416 corresponding to the new first side chain block 414 may besigned (e.g., via a digital signature algorithm). In such an embodiment,the first check may comprise validating the public key certificate chainof the certificate used to sign the one or more blocks 404 and verifythe signature applied to the one or more blocks 404. Variousverifications of the blocks 404 of the first set 416 may be performed invarious embodiments, as appropriate for the application.

After completing the first check, the first entity/party computingentity may write a new first side chain block 414 and cause the newfirst side chain block 414 to be written to the first side chain 412. Inan example embodiment, writing a first side chain block 414 to the firstside chain 412 requires the first side chain block 414 to pass aconsensus and/or voting process, as are generally known in thedistributed ledger art, corresponding to the primary blockchain 402and/or to the first side chain 412 itself. In an example embodiment,first side chain blocks 414 may be written to the first side chain 412without invocation of a consensus and/or voting process. In variousembodiments, writing the first side chain block 414 to the first sidechain 412 comprises using a non-PQC technique to encrypt at least aportion of the first side chain block 414. In various embodiments,writing the first side chain block 414 to the first side chain 412comprises signing the first side chain block 414 using a first digitalsignature algorithm. In an example embodiment, the first digitalsignature algorithm is a non-PQC digital signature algorithm.

At step/operation 506, the first entity/party computing entity may writea second side chain block 424 corresponding to a second set 426 ofblocks 404 of the primary blockchain 402 and/or the side chain blocks414 corresponding to the blocks 404 of the second set 426 (e.g., viaprocessing circuitry 202, memory 204, communication circuitry 208,and/or the like). For example, the first entity/party computing entitymay determine that a new second set 426 of blocks 404 has been added tothe primary block chain 404. This new second set 426 of blocks 404 maybe used to generate a new second side chain block 424. For example, itmay be determined that Y blocks 404 have been written to the primaryblock chain 404 since a second side chain block 424 was written to thesecond side chain 422 and/or since the last block 404 of the immediatelyprevious second set 426 of blocks 404 was written to the primaryblockchain 402. In an example embodiment, this determination may triggera second check to be performed. In an example embodiment, the secondcheck may include generating a hash of one or more blocks 404 of thesecond set 426 corresponding to the new second side chain block 424 andcomparing that hash to a hash (e.g., link 618) contained in animmediately succeeding block 404. In an example embodiment, the secondcheck may include generating a hash of one or more first side chainblocks 414 corresponding to the blocks 404 of the second set 426corresponding to the new second side chain block 424 and comparing thathash to a hash (e.g., link 628) contained in an immediately succeedingfirst side chain block 414. If the hashes match, the second check maydetermine that the one or more blocks 404 and/or first side chain blocks414 are verified. In an example embodiment, the one or more blocks 404of the second set 426 corresponding to the new second side chain block424 may be signed (e.g., via a digital signature algorithm). In such anembodiment, the second check may comprise validating the public keycertificate chain of the certificate used to sign the one or more blocks404 and verify the signature applied to the one or more blocks 404. Invarious embodiments, the first side chain blocks 414 that correspond tothe blocks 404 of the second set 426 corresponding to the new secondside chain block 424 are signed (e.g., via a digital signaturealgorithm) and the second check comprises confirming the signatureapplied to the first side chain blocks 414 corresponding to the blocks404 of the second set 426. Various verifications of the blocks 404 ofthe second set 426 and/or the corresponding first side chain blocks 414may be performed in various embodiments, as appropriate for theapplication.

After completing the second check, the first entity/party computingentity may write a new second side chain block 424 and cause the newsecond side chain block 424 to be written to the second side chain 422.In an example embodiment, writing a second side chain block 424 to thesecond side chain 422 requires the second side chain block 424 to pass aconsensus and/or voting process, as are generally known in thedistributed ledger art, corresponding to the primary blockchain 402and/or to the second side chain 422 itself. In an example embodiment,second side chain blocks 424 may be written to the second side chain 422without invocation of a consensus and/or voting process. In variousembodiments, writing the second side chain block 424 to the second sidechain 422 comprises using a non-PQC technique to encrypt at least aportion of the second side chain block 424. In various embodiments,writing the second side chain block 424 to the second side chain 422comprises signing the second side chain block 424 using a second digitalsignature algorithm. In an example embodiment, the second digitalsignature algorithm is a PQC digital signature algorithm. In variousembodiments, generating a second side chain block 424 may cause asignature 626 applied to a first side chain block 414 to be encapsulatedwith a PQC signature within a second side chain block 424.

In various embodiments, the process may continue in a continuous manner.For example, the stream of information/data may continue to be received,generated, monitored, and/or the like such that new blocks 404 arewritten to the primary blockchain 402 in a continuous manner. In anexample embodiment, once another first set 416 of X blocks 042 are addedto the primary blockchain 402, a new first side chain block 414 isgenerated and written to the first side chain 412. In an exampleembodiment, once another second set 426 of Y blocks 404 are added to theprimary blockchain 402, a new second side chain block 424 is generatedand written to the second side chain 422. In various embodiments, theinteger X may be selected such that time needed to complete the processof generating and writing a new first side chain block 414 to the firstside chain 412 is approximately equal to the average length of time thatit takes for X block 404 to be written to the primary blockchain 404. Inthis manner, the first side chain 412 may be updated in real time ornear real time with the generation of a first set of blocks 404 of theprimary blockchain 402. In various embodiments, the integer Y may beselected such that time needed to complete the process of generating andwriting a new second side chain block 424 to the second side chain 422is approximately equal to the average length of time that it takes for Yblock 404 to be written to the primary blockchain 404. In this manner,the second side chain 422 may be updated in real time or near real timewith the generation of a second set of blocks 404 of the primaryblockchain 402. In various embodiments, a first or second side chain412, 422 may be generated for an existing blockchain 402. For example,in an example embodiment, the first and/or second side chain blocks 414,424 may be generated some time (e.g., minutes, hours, days, months,years) after the corresponding blocks 404 of the primary block chain402.

In various embodiments, the first side chain 412 may be used to performa verification of information/data stored in the primary blockchain 402and/or the second side chain 422 may be used to perform verification ofinformation/data stored in the primary blockchain 402 and/or the firstside chain 412. In an example embodiment, the first and/or second sidechain 412, 422 may be used to verify that the primary blockchain 402 hasnot be corrupted and/or modified (e.g., via comparison of the first andsecond side chains, and/or the like). For example, using appropriatecryptographic keys, the first and/or second side chain blocks 414, 424may be decrypted, hashed, and/or have the signatures 626, 636 thereofverified. Additionally, the second side chain 422 is protected fromtampering and/or corruption using at least one PQC technique such thatthe second side chain 422 may be trusted as a verified source. In anexample embodiment, the first and/or second side chain 412, 422 may alsobe used to track when and by whom blocks of the primary blockchain 402and/or the first side chain 412 are accessed. Thus, various embodiments,provide for verification of information/data stored in blockchain and/oranother ledger, similar to as described U.S. Pat. No. 10,419,209, issuedSep. 17, 2019. However, various embodiments provide the improvements ofbeing able to verify the non-PQC encrypted and/or signed first sidechain 412 using the PQC encrypted and/or signed second side chain 422,PQC level protection for information/data and verification thatinformation/data of the primary block chain and/or first side chain havenot been tampered with and/or corrupted, and/or provide a migration pathfrom non-PQC techniques for protecting information/data to PQCtechniques and/or PQC enabled systems for protecting information/data.

Although various embodiments are described herein as relating to ablockchain, various embodiments may correspond to a variety of ledgers.For example, a primary ledger may be maintained and first and secondside ledgers may be generated based thereon. In various embodiments, theprimary ledger and/or the first and/or second side ledgers may bedistributed ledgers (e.g., local copies of which are stored by aplurality of computing entities). In various embodiments, the ledger maynot be a distributed ledger. For example, the primary ledger may bestored only by the first entity/party computing entity (e.g., ratherthan in a distributed manner by a plurality of computing entities) andthe first and/or second side chains may be stored by the external datarepository 120.

Encryption Bundle

In various embodiments, an information/data instance may be stored in anexternal data repository and/or disseminated through an external datarepository as part of an encryption bundle. In various embodiments, anencryption bundle comprises an encrypted information/data instance and adecryption application. In various embodiments, a decryption applicationis a self-contained application that is configured to decrypt theencrypted information/data instance. For example, a plaintext (e.g., inthe clear and/or unencrypted text) information/data instance may beencrypted using a particular cryptographic technique and using aparticular cryptographic key. A corresponding decryption application maythen be generated based on the particular cryptographic technique andthe particular cryptographic key. In an example embodiment, generating adecryption application based in part on a particular cryptographic keycomprises generating the decryption algorithm based at least in part ona private key that is private counterpart to the particularcryptographic key.

In various embodiments, the encrypted information/data instance and thedecryption application are bundled together to form an encryptionbundle. For example, the decryption application and encryptedinformation/data instance may be stored together in a file or folder,stored compressed together in a file or folder, stored within a commondata structure, and/or the like. For example, the encryption bundle maybe configured to be provided (e.g., transmitted) as a single unit ratherthan as distinct components.

In various embodiments, the decryption application is self-contained,meaning that the decryption algorithm may be fully executed without theuse of any libraries outside of the decryption application. For example,everything needed to fully execute the decryption application iscontained within the decryption application and the decryptionapplication need only read the encrypted information/data instance and,possibly, receive at least one credential. In various embodiments, thedecryption application is compiled prior to the bundling of thedecryption application and the encrypted information/data instance.

As noted previously, the decryption application may be configured toreceive at least one credential. For example, execution of thedecryption application by the processing circuitry of a computing entitymay cause the decryption application to request a passcode, biometricmarker, authentication token, and/or other credential. The decryptionapplication may be configured to receive the at least one credential viauser interaction with a user interface (e.g., input/output circuitry) ofthe computing entity, by accessing a credential stored in memory of thecomputing entity, and/or the like. The decryption application may thenuse the received at least one credential to authorize the decryption ofthe encrypted information/data instance. For example, the decryptionapplication may use the received at least one credential to complete adecryption key, decrypt a decryption key, ensure that a user (e.g.,human user and/or machine user) is authorized to access the decryptedencrypted information/data instance, and/or the like such that thedecryption application may use the decryption key to decrypt thecorresponding encrypted information/data instance.

In various embodiments, the encryption bundle is used to disseminateinformation/data instances in a secure manner. For example, a firstparty may provide an encryption bundle for storage in an external datarepository 120 and provide a second party with the at least onecredential. In various embodiments, the first party provides the atleast one credential to the second party via a communication channelthat does not include the external data repository 120. The second partymay then access the encryption bundle from the external data repository120 and use the at least one credential and the decryption applicationof the encryption bundle to decrypt the encrypted information/datainstance. In various embodiments, an encryption bundle may be used todisseminate information/data instances securely between a first partyand one or more second parties, between one second party and one or moreother second parties, and/or the like. For example, the encryptionbundle may in effect simplify key management for securelysharing/disseminating information/data between multiple parties via anexternal data repository 120. For example, access to theinformation/data of the encrypted information/data instance may bemanaged through out of channel (e.g., via a communication channel thatdoes not include the external data repository 120) sharing of the atleast one credential.

In various embodiments, the encryption bundle is a backward compatible.For example, an information/data instance may be encrypted usingEncryption Algorithm 1.0. At a later point in time, the standard PQCtechnique may be Encryption Algorithm 1.7. Thus, various computingentities (e.g., a first entity/party computing entity and/or secondentity/party computing entity) may have been updated to encrypted and/ordecrypt information/data using Encryption Algorithm 1.7. However, sincethe decryption application is self-contained, the various computingentities may still decrypt the encrypted information/data from theencryption bundle comprising the decryption algorithm.

FIG. 9 provides a flowchart illustrating various processes, procedures,operations, and/or the like of a method 900 that may be performed by afirst entity/party computing entity and/or a second entity/partycomputing entity (e.g., a PQC system 102, PQC server device 104, PQCdatabase 106, server device 110, client device 112, database serverdevice 114, remote server device 116, apparatus 200, 280, 290, PQCsystem 302, and/or client device 320, 330, 340, 350, 360) to generate anencryption bundle and provide the encryption bundle for storage by anexternal data repository 120. Starting at step/operation 902, a first orsecond entity/party computing entity receives or generates (e.g., viaprocessing circuitry 202, communication circuitry 208, and/or the like)an information/data instance. For example, the information/data instancemay be generated and/or received via a stream of information/data (e.g.,transaction information/data), based on execution of an applicationand/or program by the first or second entity party computing entity,received via a communication from another computing entity, and/or thelike. In various embodiments, the first or second entity/party computingentity may determine and/or receive an indication that theinformation/data instance should be encrypted and stored/disseminated aspart of an encryption bundle.

At step/operation 904, the first or second entity/party computing entityencrypts the information/data instance (e.g., via processing circuitry202, cryptographic circuitry 248, and/or the like) to generate anencrypted information/data instance. For example, the information/datainstance may be encrypted using a particular cryptographic technique(e.g., a PQC technique). In an example embodiment, the information/datainstance is encrypted using the particular cryptographic technique usinga particular cryptographic key.

At step/operation 906, the first or second entity/party computing entitygenerates a decryption application corresponding to the encryptedinformation/data instance (e.g., via processing circuitry 202, and/orthe like). In an example embodiment, the decryption application isgenerated at least in part based on the particular cryptographictechnique. For example, the decryption application may be an applicationthat is configured to decrypt encrypted information/data using adecryption algorithm corresponding to the particular cryptographictechnique. In an example embodiment, the decryption application isgenerated based at least in part on the particular cryptographic key.For example, in an example embodiment, the decryption applicationcomprises the particular cryptographic key and/or a private key that isthe private counterpart to the particular cryptographic key. In anexample embodiment, the decryption application is generated based on atleast one credential. For example, the decryption application may beconfigured to complete a decryption key (e.g., the particularcryptographic key and/or a private counterpart thereto) based on the atleast one credential, decrypt the decryption key based on the at leastone credential, determine that a user (e.g., human user or machine user)is authorized to access the decrypted encrypted information/datainstance, and/or the like based on receiving the at least onecredential.

In an example embodiment, the decryption application is generated basedon a pre-programmed application format and/or template. In an exampleembodiment, the application format and/or template comprises computerexecutable code configured to perform a decryption algorithmcorresponding to the particular cryptographic technique. In an exampleembodiment, the application format and/or template comprises computerexecutable code configured to request at least one credential andreceive at least one credential. In an example embodiment, theapplication format and/or template is self-contained, meaning that itdoes not reference any external libraries. Generating the decryptionapplication may include linking the particular cryptographic key or aprivate key that is the private counterpart to the particularcryptographic key and the at least one credential to the applicationformat and/or template. The application format and/or template with theparticular cryptographic key and/or private counterpart thereof and theat least one credential linked may then be compiled to generate theself-contained decryption application.

At step/operation 908, the first or second entity/party computing entitybundles the encrypted information/data instance and the correspondingdecryption application to generate an encryption bundle (e.g., viaprocessing circuitry 202). For example, the encrypted information/datainstance and corresponding decryption application may be stored togetherin a file or folder, stored compressed together in a file or folder,stored within a common data structure, and/or the like to form theencryption bundle.

At step/operation 910, the first or second entity/party computing entityprovides (e.g., transmits) the encryption bundle such that the externaldata repository 120 receives and stores the encryption bundle in memorythereof. For example, the first or second entity/party computing mayprovide (e.g., via processing circuitry 202, communication circuitry208, and/or the like) the encryption bundle. The external datarepository 120 may receive the encryption bundle and store theencryption bundle. In an example embodiment, the encryption bundle maycomprise and/or be associated with metadata comprising authorizationinformation/data. For example, the authorization information/data mayindicate which parties/entities are authorized to access the encryptionbundle stored in the external data repository 120.

FIG. 10 provides a flowchart illustrating various processes, procedures,operations, and/or the like of a method 1000 that may be performed by afirst entity/party computing entity and/or a second entity/partycomputing entity (e.g., a PQC system 102, PQC server device 104, PQCdatabase 106, server device 110, client device 112, database serverdevice 114, remote server device 116, apparatus 200, 280, 290, PQCsystem 302, and/or client device 320, 330, 340, 350, 360) to access aninformation/data instance via an encryption bundle stored by an externaldata repository 120.

Starting at step/operation 1002, a first or second entity/partycomputing entity access an encryption bundle stored by the external datarepository 120 (e.g., via processing circuitry 202, communicationscircuitry 208, and/or the like). For example, the first or secondentity/party computing entity 120 may provide and/or submit a requestfor the encryption bundle such that the request is received by theexternal data repository 120. The external data repository 120 mayreceive and process the request and, responsive thereto and/or todetermining that the first or second computing entity is authorized toreceive the encryption bundle (e.g., based on metadata and/orauthorization information/data corresponding to the encryption bundle),provide the encryption bundle such that the first or second entity/partycomputing entity receives the encryption bundle. For example, the firstor second entity/party computing entity may receive the encryptionbundle.

At step/operation 1004, the first or second entity/party computingentity may initiate execution of the decryption application of theencryption bundle (e.g., via processing circuitry 202, memory 204,and/or the like). For example, the first or second entity/partycomputing entity may extract, decompress, and/or the like (asappropriate) from the decryption application from the encryption bundle.An executable of the decryption application may be identified (e.g.,based on type, file extension, and/or the like associated therewith) andthe executable of the decryption application may be initiated. In anexample embodiment, the executable of the decryption application isconfigured to automatically initiate responsive to the decryptionapplication being extracted, decompressed, and/or the like from theencryption bundle.

In an example embodiment, initiating the execution of the decryptionapplication (e.g., the executable of the decryption application) maycause the decryption application to check the memory (e.g., memory 204)of the first or second entity/party computing entity to determine if acopy of the decryption application is present in the memory. In anexample embodiment, if the decryption application finds a copy of itselfin the memory, the execution of the decryption application may exit andmay provide an error. For example, the decryption application may be aone time/single use application (and/or limited use application) thatcannot be used multiple times by the same computing entity (e.g., to trydifferent credentials and/or the like). In an example embodiment, thedecryption application comprises a counter and the counter may beincremented to indicate that that instance of the decryption applicationis being executed by the first or second entity/party computing entity.In an example embodiment, the counter may be set to zero or anotherinitial value when the decryption application is generated. In anexample embodiment, when the counter reaches a threshold value (e.g.,one, two, three, or a certain amount greater than the initial value),the decryption application may, upon initiation of execution thereof andchecking of the counter, exit and provide an error. For example, thedecryption application may be configured to only execute a certainnumber of times. Thus, in various embodiments, the decryptionapplication may be configured to prevent unauthorized access to thedecrypted encrypted information/data instance caused by a user guessingat the at least one credential.

In various embodiments, initiation of the execution of the decryptionapplication (e.g., an executable of the decryption application) maycause the first or second entity/party computing entity to request atleast one credential. For example, the at least one credential may be apasscode, biometric marker, authentication token, and/or othercredential. For example, the entity/party that generated the encryptionbundle may have provided the first or second entity/party with the atleast one credential via a communication channel that does not includethe external data repository 120. The first or second entity/partycomputing entity may provide the request for the at least one credentialand receive user input (and/or indication thereof) providing the atleast one credential via input-output circuitry 206, UI circuitry 258,and/or the like. In another example, the decryption application may beconfigured to provide an API call and/or the like to an operating systemof the first or second entity/party computing entity to access the atleast one credential stored in memory (e.g., memory 204) of the first orsecond entity/party computing entity.

At step/operation 1006, the first or second entity/party computingentity passes the at least one credential to the decryption application.For example, the at least one credential may be provided to thedecryption application. The decryption application may then execute touse the at least one credential to determine that a user (e.g., thefirst or second entity/party) is authorized to access the decryptedencrypted information/data instance, to use the at least one credentialto generate and/or complete a decryption key, to decrypt a decryptionkey, and/or the like.

At step/operation 1008, the first or second entity/party computingentity continues to execute the decryption application such that thedecryption application. For example, the decryption application mayaccess (read, extract, decompress, and/or the like) the encryptedinformation/data instance of the encryption bundle and use acryptographic technique and the decryption key (e.g., the particularcryptographic key and/or a private key that is the private counterpartof the particular cryptographic key) to decrypt the encryptedinformation/data instance. In various embodiments, the decryptionapplication uses a PQC technique to decrypt the encryptedinformation/data instance.

At step/operation 1010, the first or second entity/party computingentity continues to execute the decryption application such that thedecrypted encrypted information/data instance is provided. For example,the decrypted encrypted information/data instance may be provided via aUI (e.g., via input-output circuitry 206, UI circuitry 258, and/or thelike). For example, the decrypted encrypted information/data instancemay be displayed via a graphical user interface. In another exampleembodiment, the decrypted encrypted information/data instance may beadded (e.g., by processing circuitry 202) to database stored in memory(e.g., memory 204) stored by and/or accessible to the first or secondentity/party computing entity. In an example embodiment, the decryptedencrypted information/data instance may be provided to an application orprogram operating on the first or second entity/party computing entity,for example, to perform and/or process a transaction, and/or the like.

Thus, in various embodiments, an encryption bundle may be used to storeinformation/data in a secure manner with backward compatible decryptionabilities. In various embodiments, an encryption bundle may be used todisseminate information/data to between a first party and one or moresecond parties and/or between two or more second parties via an externaldata repository 120 operated by a third party without the third-partyhaving access to the content of the information/data and withoutrequiring a complex key management scheme. Moreover, the data storedwithin an encryption bundle may be safe from cryptanalytic algorithmsimplemented on a quantum computer due to the use of PQC techniques toencrypt the information/data instance and the limited number of timesthe decryption application may be executed, in various embodiments.

Technical Advantages

Various embodiments provide a variety of technical advantages. Inparticular, various embodiments provide technical advantages related tothe secure storage of information/data by an external data repositorythat is not operated by and/or on behalf of the data owner and/or thatis only operated in part by and/or on behalf of the data owner (e.g., asmay be the case in various distributed ledger and/or blockchainplatforms). Moreover, example embodiments provide a migration path fromnon-PQC techniques for protecting information/data to PQC techniquesand/or PQC enabled systems for protecting information/data.

For example, various embodiments provide two or more side chains/ledgerfor a primary blockchain/ledger. For example, the two or more sidechains enable the verification of the non-PQC encrypted and/or signedfirst side chain using the PQC encrypted and/or signed second sidechain. Additionally, various embodiments provide PQC level protectionfor information/data and/or PQC level verification that information/dataof the primary block chain and/or first side chain have not beentampered with and/or corrupted. Additionally, example embodimentsprovide a migration path from non-PQC techniques for protectinginformation/data to PQC techniques and/or PQC enabled systems forprotecting information/data.

Thus, various embodiments provide technical solutions to the technicalproblem of securely storing information/data in an external datarepository (e.g., cloud-based storage and/or the like) in a manner thatis resistant to cryptanalytic algorithms implemented on a quantumcomputer. Moreover, various embodiments provide technical solutions totechnical problems related to cryptographic key management whenencrypted information/data is being disseminated via an external datarepository and technical problems related to migrating from non-PQCsystems and/or data protection protocols to PQC and/or data protectionprotocols.

CONCLUSION

While various embodiments in accordance with the principles disclosedherein have been shown and described above, modifications thereof may bemade by one skilled in the art without departing from the teachings ofthe disclosure. The embodiments described herein are representative onlyand are not intended to be limiting. Many variations, combinations, andmodifications are possible and are within the scope of the disclosure.Alternative embodiments that result from combining, integrating, and/oromitting features of the embodiment(s) are also within the scope of thedisclosure. Accordingly, the scope of protection is not limited by thedescription set out above, but is defined by the claims which follow,that scope including all equivalents of the subject matter of theclaims. Each and every claim is incorporated as further disclosure intothe specification and the claims are embodiment(s) of the presentdisclosure. Furthermore, any advantages and features described above mayrelate to specific embodiments but shall not limit the application ofsuch issued claims to processes and structures accomplishing any or allof the above advantages or having any or all of the above features.

In addition, the section headings used herein are provided forconsistency with the suggestions under 37 C.F.R. § 1.77 or to otherwiseprovide organizational cues. These headings shall not limit orcharacterize the disclosure set out in any claims that may issue fromthis disclosure. For instance, a description of a technology in the“Background” is not to be construed as an admission that certaintechnology is prior art to any disclosure in this disclosure. Neither isthe “Summary” to be considered as a limiting characterization of thedisclosure set forth in issued claims. Furthermore, any reference inthis disclosure to “disclosure” or “embodiment” in the singular shouldnot be used to argue that there is only a single point of novelty inthis disclosure. Multiple embodiments of the present disclosure may beset forth according to the limitations of the multiple claims issuingfrom this disclosure, and such claims accordingly define the disclosure,and their equivalents, that are protected thereby. In all instances, thescope of the claims shall be considered on their own merits in light ofthis disclosure but should not be constrained by the headings set forthherein.

Also, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other devices or components shown or discussed as coupled to, or incommunication with, each other may be indirectly coupled through someintermediate device or component, whether electrically, mechanically, orotherwise. Other examples of changes, substitutions, and alterations areascertainable by one skilled in the art and could be made withoutdeparting from the scope disclosed herein.

Many modifications and other embodiments of the disclosure set forthherein will come to mind to one skilled in the art to which theseembodiments pertain having the benefit of teachings presented in theforegoing descriptions and the associated figures. Although the figuresonly show certain components of the apparatus and systems describedherein, it is understood that various other components may be used inconjunction with the PQC system. Therefore, it is to be understood thatthe disclosure is not to be limited to the specific embodimentsdisclosed and that modifications and other embodiments are intended tobe included within the scope of the appended claims. For example, thevarious elements or components may be combined, rearranged, orintegrated in another system or certain features may be omitted or notimplemented. Moreover, the steps in any method described above may notnecessarily occur in the order depicted in the accompanying figures, andin some cases one or more of the steps depicted may occur substantiallysimultaneously, or additional steps may be involved. Although specificterms are employed herein, they are used in a generic and descriptivesense only and not for purposes of limitation.

What is claimed is:
 1. A method for operating a ledger system, themethod comprises: accessing, by a computing entity, one or more blocksof a blockchain comprising a plurality of blocks, the plurality ofblocks comprising one or more non-overlapping first sets of blocks, eachfirst set comprising a first number of consecutive blocks, the one ormore blocks being from a particular one of the one or more first sets;encrypting, by the computing entity, the content of the one or moreblocks using a first cryptographic technique to generate one or morefirst encrypted block values; writing, by the computing entity, a firstside chain block comprising the one or more first encrypted block valuesand a first signature to a first side chain; accessing, by the computingentity, at least one of (a) at least one block of a particular secondset of one or more second sets of the plurality of blocks or (b) one ormore first side chain blocks corresponding to blocks of the particularsecond set, wherein the second sets are mutually non-overlapping andeach comprise a second number of consecutive blocks of the plurality ofblocks; encrypting, by the computing entity, the content of at least oneof (a) the at least one block or (b) the one or more first side chainblocks using a second cryptographic technique to generate at least onesecond encrypted block value; writing, by the computing entity, a secondside chain block comprising the at least one second encrypted blockvalue and a second signature to a second side chain.
 2. The method ofclaim 1, wherein the second cryptographic technique is a post quantumencryption.
 3. The method of claim 2, wherein the second number islarger than the first number.
 4. The method of claim 1, wherein at leastone of the first side chain or the second side chain are generated inreal time or near real time with respect to blocks of the particular oneof the one or more first sets being written to the blockchain.
 5. Themethod of claim 1, wherein each of the blocks of the blockchain, thefirst side chain, and the second side chain comprise a link to animmediately previous block of the corresponding blockchain, first sidechain, and second side chain, respectively.
 6. The method of claim 5,wherein the link is a hash of the immediately previous block.
 7. Themethod of claim 1, further comprising: receiving, by the computingentity, instances of data; and writing, by the computing entity, blockscomprising the instances of data to the blockchain.
 8. The method ofclaim 1, wherein the computing entity performs a verification of atleast one of one or more instances of data in the one or more blocksbefore encrypting the content of the one or more blocks using the firstcryptographic technique.
 9. The method of claim 1, wherein the computingentity performs a verification of the first signature of a first sidechain block before encrypting or the first side chain block using thesecond cryptographic technique.
 10. An apparatus for operating at leasta portion of a ledger system, the apparatus comprising: processorcircuitry configured to: access one or more blocks of a blockchaincomprising a plurality of blocks, the plurality of blocks comprising oneor more non-overlapping first sets of blocks, each first set comprisinga first number of consecutive blocks, the one or more blocks being froma particular one of the one or more first sets; encrypt the content ofthe one or more blocks using a first cryptographic technique to generateone or more first encrypted block values; write a first side chain blockcomprising the one or more first encrypted block values and a firstsignature to a first side chain; access at least one of (a) at least oneblock of a particular second set of one or more second sets of theplurality of blocks or (b) one or more first side chain blockscorresponding to blocks of the particular second set, wherein the secondsets are mutually non-overlapping and each comprise a second number ofconsecutive blocks of the plurality of blocks; encrypt the content of atleast one of (a) the at least one block or (b) the one or more firstside chain blocks using a second cryptographic technique to generate atleast one second encrypted block value; write a second side chain blockcomprising the at least one second encrypted block value and a secondsignature to a second side chain.
 11. The apparatus of claim 10, whereinthe second cryptographic technique is a post quantum encryption.
 12. Theapparatus of claim 11, wherein the second number is larger than thefirst number.
 13. The apparatus of claim 10, wherein at least one of thefirst side chain or the second side chain are generated in real time ornear real time with respect to blocks of the particular one of the oneor more first sets being written to the blockchain.
 14. The apparatus ofclaim 10, wherein each of the blocks of the blockchain, the first sidechain, and the second side chain comprise a link to an immediatelyprevious block of the corresponding blockchain, first side chain, andsecond side chain, respectively.
 15. The apparatus of claim 14, whereinthe link is a hash of the immediately previous block.
 16. The apparatusof claim 10, wherein the processing circuitry is further configured to:receive instances of data; and write blocks comprising the instances ofdata to the blockchain.
 17. The apparatus of claim 10, wherein theprocessing circuitry is further configured to perform a verification ofat least one of one or more instances of data in the one or more blocksbefore encrypting the content of the one or more blocks using the firstcryptographic technique.
 18. The apparatus of claim 10, wherein theprocessing circuitry is further configured to perform a verification ofthe first signature of a first side chain block or the first side chainblock before encrypting the first side chain block using the secondcryptographic technique.
 19. A computer program product comprising atleast one non-transitory storage media storing executable instructions,the executable instructions comprising executable code portionsconfigured to, when executed by the processing circuitry of anapparatus, cause the apparatus to: access one or more blocks of ablockchain comprising a plurality of blocks, the plurality of blockscomprising one or more non-overlapping first sets of blocks, each firstset comprising a first number of consecutive blocks, the one or moreblocks being from a particular one of the one or more first sets;encrypt the content of the one or more blocks using a firstcryptographic technique to generate one or more first encrypted blockvalues; write a first side chain block comprising the one or more firstencrypted block values and a first signature to a first side chain;access at least one of (a) at least one block of a particular second setof one or more second sets of the plurality of blocks or (b) one or morefirst side chain blocks corresponding to blocks of the particular secondset, wherein the second sets are mutually non-overlapping and eachcomprise a second number of consecutive blocks of the plurality ofblocks; encrypt the content of at least one of (a) the at least oneblock or (b) the one or more first side chain blocks using a secondcryptographic technique to generate at least one second encrypted blockvalue; write a second side chain block comprising the at least onesecond encrypted block value and a second signature to a second sidechain.
 20. The computer program product of claim 19, wherein the secondcryptographic technique is a post quantum encryption and the secondnumber is larger than the first number.